-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
Expose overrides as a cli flag #32
Comments
The concept of a "template" is used in pandoc (and many other places) for something that would get filled by the fragment created by renderHTML to produce a "standalone" document. See the User's Guide In pandoc these templates can have variables that are filled, e.g., by metadata or programatically. I think it would be confusing to use the name "template" for this different thing, so I'd prefer to stick with "overrides" (or maybe there's a better name). |
Note that you can take advantage of pandoc's templates already:
should give you nice output. |
On the one hand, yes, on the other hand, I feel like overrides are not that different, as they are a generalization of the idea. Pandoc's template is an an override for the root From another angle, asciidoctor-web is using No super-strong opinion here. An obvious solution is to expose |
#4 added an ability to customize html rendering. It only added programmatic API, but we should expose this as a CLI as well.
I think a good name for the flag would be
--html-template slides.js
(might also rename "overrides" to "template" in the API).The text was updated successfully, but these errors were encountered: