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

Add support for inline roles to theme #368

mojavelinux opened this Issue Dec 9, 2015 · 3 comments


None yet
2 participants

mojavelinux commented Dec 9, 2015

Allow the theme to control the styling for roles on inline elements. When a role is detected on an inline element, it consults the theme to get styling information to merge into the default. This effectively brings styling using CSS classes to inline elements.


[.type]#name of type#

@mojavelinux mojavelinux added this to the v1.5.0.beta.1 milestone Dec 9, 2015

@mojavelinux mojavelinux self-assigned this Feb 14, 2016


This comment has been minimized.


mojavelinux commented Feb 14, 2016

We also may want to define some built-in, semantic role names as discussed in asciidoctor/asciidoctor#1664.


This comment has been minimized.

mattwynne commented Nov 9, 2018

Given that this issue is still open, is there any way at the moment for me to style individual pages or other elements in a PDF, e.g. adding a different background image to each level 1 section?

No criticism or pressure meant - I work a lot on OSS myself and I know you need to be free to just get around to things when you can. I'm just new to asciidoctor and trying to get my head around the scope of what's possible. In general it seems like an awesome piece of work so far, so thanks very much.


This comment has been minimized.

mattwynne commented Nov 12, 2018

@mojavelinux I dunno how hard this is or how much bandwidth you have, but I am feeling the pain of this right now and would be motivated to have a crack at implementing it myself if you were able to give me some pointers.

I'm going to experiment with using a custom converter (as mentioned in #337) for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment