ethanmuller / assemble-atomic Goto Github PK

Right now, permalinks look like this:

patterns/patternType-patternGroup/patternName/index.html

e.g.

patterns/atom-headings/large-heading/index.html

This seems really goofy. You know what'd be cool?

patterns/patternType/patternGroup/patternName.html

e.g.

patterns/atoms/headings/large-heading.html

And maybe the groups could even have an index file that lists out all the patterns in that group.

There's probably a reason it's not being done this way already, but this seems a lot more intuitive.

Add more options to pass data to patterns, as well as ways to override the data we pass. Here they are, ordered by priority.

All of these examples would output a heading with the text of "I am a heading".

Block data

{{#atom 'heading'}}I am a heading{{/atom}}

Note: passing data as a block like this would be setting the outlet property to the text inside the block. All other examples are setting text.

Inline data

{{atom 'heading' text='I am a heading'}}

Passed context

# where current context is this:
heading_data:
  text: 'I am a heading'

{{atom 'heading' heading_data}}

Pattern YFM
Imagine a block of YFM at the top of a pattern's handlebars file. Useful for setting defaults.

Current context

# where current context is this:
text: 'I am a heading'

{{atom 'heading'}}

I like the way Pattern Lab does ordering. You order pattern types, groups, and patterns by adding a number at the beginning of the filename. You don't need to include the number when you include it. And it's optional. If you leave out the number, it'll go alphabetically.