Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Styles only in text/preview #115

Open
stinoga opened this issue Feb 26, 2014 · 4 comments
Open

Styles only in text/preview #115

stinoga opened this issue Feb 26, 2014 · 4 comments

Comments

@stinoga
Copy link

stinoga commented Feb 26, 2014

After generating my styleguide with LESS, the outputted styles are only inside of a style tag with the text/preview type. This causes the examples in my styleguide to not have any styling.

@marrs
Copy link
Collaborator

marrs commented Mar 2, 2014

What happens if you compile the LESS to CSS first and then build the docs with that?

@stinoga
Copy link
Author

stinoga commented Mar 13, 2014

Neither seem to work. Either way, I'd like to compile my styleguide from LESS, as I'd like to compile it from modules in a specific folder.

@peebeebee
Copy link

I got the same problem. No iframe's to be seen.

EDIT: Found something... Styledocco 'crashes' fairly easily without giving any warnings when the comments are not perfect.
Ex.:

/** Two asterisks in the beginning will make Styledocco crash */
/* Not having four spaces before iframe content like below, will also crash StyleDocco
<a class="btn">Button</a>
*/

EDIT2: Also, if you don't use the preprocessor option from StyleDocco, and just build your stylesheets with Less/Sass, the comments will be realigned, resulting in StyleDocco crashing.

@marrs
Copy link
Collaborator

marrs commented May 20, 2014

Thanks for raising these issues. If you're able to provide patches, that would be great. I'm unable to find the time to work on Styledocco at the moment but I am merging pull requests if they come with unit tests and don't break the build. I've refactored the code in develop so that the formatting of comments can be clearly documented/tested and separated from the rest of the process chain. I knew about the 4 spaces issue, but not about the other 2. I will raise separate tickets for them at some point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants