I've been using Jekyll for technical documentation but am exploring Asciidoctor based on some challenges with Jekyll. However, I am not sure if the challenges can be solved with Asciidoctor either. I'd like to ask some basic Asciidoctor questions to see if someone can help guide me.
Does Asciidoctor always output the entire guide on one page, with an on-page TOC to jump to different headings on that page? How do I generate a traditional table of contents that allows users to navigate to different pages? If I have 30 different outputs (for different products, versions, etc.) from the same core set of files, how would I do that with Asciidoctor? Is there an equivalent to the configuration file used in Jekyll or something? If some files relate to one product but not another, how do you suppress some of those files from being generated in the other outputs? Is it possible to create a JSON output with Asciidoctor? Suppose I want to do something similar to collections in Jekyll. Does Asciidoctor offer anything like that? I find that the JSON output is handy for tooltips. Thanks, Tom -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
