-
Notifications
You must be signed in to change notification settings - Fork 86
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
Publish or bundle styles so that they can be consumed by tools #27
Comments
I'd suggest compiling, zipping and auto-deploying the styles to Github Releases using Travis CI. The same approach is useful for automatically publishing the stylesheet previews (themes.asciidoctor.org), which are now living in the |
By sniffing out the sources on http://themes.asciidoctor.org/preview/ I found the location of some of the CSS files. For example, http://themes.asciidoctor.org/stylesheets/asciidoctor.css?v=8 I've been trying to use these style bundles in norganna/adoc-usermacro#5 to get access to some form of css styles that are hosted somewhere. But I think my idea of what constitutes "hosted" here is wrong. That is the css file Is my understanding correct? |
The stylesheet factory is mostly a defunct experiment at this point. The stylesheets aren't maintained anymore, except for the default one. The only reason this repository still exists is to produce the default stylesheet, until we have another way. There are efforts at a reboot, but we'll likely cut out the use of Foundation just to keep it simpler and easier to maintain. In the meantime, you can find linkable stylesheets here: https://github.com/darshandsoni/asciidoctor-skins
That is the stylesheet, but I wouldn't depend on it like that. This is not a CDN. |
Currently, we aren't publishing the styles (at least not in any sort of automated fashion) so that they can be consumed by other tools. We should figure out how to do this so that these themes are available to Asciidoctor users without having to run the stylesheet factory build manually.
The text was updated successfully, but these errors were encountered: