-
Since USWDS 2.0 relies heavily on custom mixins, functions, etc, we should document them so folks can better understand what they are and how to use them.
Consider using [SassDoc](http://sassdoc.co…
maya updated
3 months ago
-
https://github.com/guardian/guss-css3/blob/master/_css3.scss#L104
-
Having a documentation made with [sassdoc](http://sassdoc.com/) would probably be a good tool for anyone wanting to change something to hmmm or a fork. It's created using comments in the code and prod…
-
At the time of writing `sass-convert` LibSass wasn't so widely used and lagged quite behind the Ruby version. Plus we couldn't really figure out how to leverage its `sass2scss` binary.
Now that it's …
-
This is related to #428 -- and really stems from CDocParser, used by scss-comment-parser, (see issued filed there: https://github.com/FWeinb/CDocParser/issues/16) -- but relates to a SassDoc use-case,…
-
Maybe it is just our SCSS Lint config, but if you are trying to add SassDoc documentation to a nested element, it won't display on the styleguide. If you instead remove the indent, then it will compil…
-
http://sassdoc.com/
-
-
Our build scripts do not properly `npm install` from the `sassdoc-theme` directory on the very first build after cloning, so any unmet dependencies for Sassdoc throw an error on a first build of Phoen…
-
Thanks to @danmurf and @dantesolis, we now have a working SassDoc generation and many components. All we need now is to link those by adding comments to newly created components !
Help can be found h…