Generic Structure about component-styleguide HOT 7 CLOSED

Thanks for checking it out, @davidhund. I like your idea and I'm happy to accept a PR for this,or make the change myself soon. Have some ideas already :-)

from component-styleguide.

Hey @davidhund, just released v1.2.0 which should contain what you proposed. It now reads all templates from the root and all subfolders, and creates menu items for each. The "root" or "generic" components menu item name can be configured with rootName.

It does not support deeply nested folders (yet), just child folders within the /components folder.

Let me know if it works for you. Thanks again for the idea.

from component-styleguide.

Just playing around it seems to do exactly what I wanted. Awesome work.
It's simple and flexible and does not force me in a specific workflow/process.

Now to find a way to extract the HTML markup from my (s)CSS comments (much like KSS) so that the markup is not disconnected from the 'source' CSS :)

from component-styleguide.

Thanks for the feedback! Let me know if you have any more ideas.

(Regarding the CSS parsing, not sure. The simplest method that could work might be to use a CSS parser and have it write the comments from the AST to HTML files in the "components" dir.)

from component-styleguide.

Yeah. I am really looking forward to a standardized CSS Comment(!) Parser.
https://twitter.com/valuedstandards/status/582504525455560704

Something like https://github.com/darcyclarke/DSS could work. This would prevent us from having to maintain markup in multiple places...

from component-styleguide.

Ah DSS looks nice. Totally JSDoc-y and useful with those @name and @markup tags etc.

from component-styleguide.

Closing this, as the initial issue is taken care of.

from component-styleguide.