-
We document [here](https://github.com/SassDoc/sassdoc/wiki/Documenting-your-items#description) that SassDoc will parse description strings as Markdown.
This is not _really_ true; today it's [the them…
-
As @FWeinb said in #120, content of the `view.json` file is definitely dependant from the theme since it's basically a set of variables passed to the view.
We need to move `view.json` to themes, and …
-
```
node_modules/sassdoc/bin/sassdoc stylesheets docs -v -c view/view.json
2014-07-17 16:58:57 Can't find a package file at `view/./package.json`.
2014-07-17 16:58:57 Folder `docs` successfully remove…
-
Hi @HugoGiraudel
Consider the following example:
``` css
/**
* Description of my variable
* ---
* @datatype string
*/
$some-other-variable: "a" !default;
/**
* Defines whether the lib should …
-
Hey,
right now the .eps version of the Sass logo is available only for latest CS (`17.0`).
http://sass-lang.com/styleguide/brand/
I would suggest to save it with a lower version compat.
I'm trying …
-
Currently `@since` is basically a _message_ annotation. You give it a message, it gets displayed. I want to change that so it has 2 parameters: a version or whatever, and optionally a message.
``` sc…
-
It would be a good idea to add a Grunt task to test compiling an empty folder so we can make sure the view works as expected when it's the case. The task should work like this:
1. Create an empty fold…
-
In the future, can Sass authors have a `.scss` or `.sass` file be parsed by SassDoc with inline comments (`//`) instead of comments that can be generated?
-
Currently, only comments beginning with `/**` and ending with `*/` are parsed. That means a comment beginning with `/*` won't be treated as documentation.
``` scss
/**
* Documentation
*/
/*
* No…
-
Idea from @fweinb, seconded by myself: https://github.com/yeoman/update-notifier.