livingstyleguide / livingstyleguide

Easily create front-end style guides with Markdown and Sass/SCSS.
https://livingstyleguide.org/
Other
871 stars 81 forks source link

more options for livingstyleguide cli #200

Open monsdroid opened 8 years ago

monsdroid commented 8 years ago

Hi,

livingstylguide fit's perfect in our project setup. especally the handlbars + md + json combination. But we dont use ruby or rails in any extend. but we dont mind using it in the build process. our build environment is node + grunt + grunt-sass the grunt-livingstyleguide plugin does what it does and calls livingstylguide for us. but how to pass variables like additional include paths or generall options for sass?

like in Issue #98 we cant get our (bower) components (breakpoint, singularity, sassy-maps, compass-mixins) to be included. in grunt-sass we add their locations as additional includePaths - no problem

how can i pass these vars to livingstyleguide if i dont have a ruby project setup?

maybe its a nice feature to be able to set all options via the cli or an option to add them to that lsg document?

e.g. livinguide.lsg

additional_import_paths:
  - "bower_components/breakpoint-sass/stylesheets/"
hagenburger commented 8 years ago

I thought about it would suggest the following, which also allows other include paths:

@load-path sass: bower_components/breakpoint-sass/stylesheets
@load-path documents: additional/path/for/lsg-documents
@load-path templates: templates

Or set a global include path (for all cases listed above):

@load-path additional/path/for/all

This will be implemented after 2.0 has been released. So it’s using the upcoming syntax (not YML).

monsdroid commented 8 years ago

as long as it is possible to pass more than one path with the new syntax this should work fine

hagenburger commented 8 years ago

Is this fine? I thought about it just adds—not replaces the load path—with each call:

@load-path sass: bower_components/breakpoint-sass/stylesheets
@load-path sass: my/second/path