JSON MetaData Content: Share between Prototype/Styleguide/CMS

kalamuna / kalastatic

:electric_plug: Facilitate the front-end experience through Styleguides and Prototypes

https://kalamuna.github.io/kalastatic/

41 stars 14 forks source link

Open thiagodemellobueno opened 7 years ago

thiagodemellobueno commented 7 years ago

@RobLoach and @thiagodemellobueno came up with some workflowy stretch goals together.

[ ] Get rid of *.metadata alltogether
[ ] Moving the mappings from config/filename.json and move to the frontmatter @ filename.md
[ ] Moving the things we actually need from config.metadata to kalastatic.yaml (we dont use much of it)

Input from @soniktrooth and @derekderaps clearly welcome appreciated

soniktrooth commented 7 years ago

The atomic name spaces don't seem to be working when it comes to metatdata stuffz.

This works: @kalastatic/components/molecules/nav--primary/nav--primary.html.json

This does not @molecules/nav--primary/nav--primary.html.json

thiagodemellobueno commented 7 years ago

Looks like we maybe able to work it into the builder in a situation where we cant go ahead and add it to KSS.

Seems like we should look at this approach for passing variables INTO kss too... and implementing our 'file injection as key' to KSS too.

RobLoach commented 6 years ago

[x] Get rid of *.metadata alltogether --- Can use .json files
[x] Moving the mappings from config/filename.json and move to the frontmatter @ filename.md -- Can use either .json or frontmatter
[ ] Moving the things we actually need from config.metadata to kalastatic.yaml (we dont use much of it)
- [ ] Add documentation around declaring globals in kalastatic.yaml
[ ] Fix @molecules usage in metadata import