Asciidoctor::Extensions
Extensions provide a way to participate in the parsing and converting phases of the AsciiDoc processor or extend the AsciiDoc syntax.
The various extensions participate in AsciiDoc processing as follows:
- After the source lines are normalized, Preprocessors modify or replace the source lines before parsing begins. IncludeProcessors are used to process include directives for targets which they claim to handle.
- The Parser parses the block-level content into an abstract syntax tree. Custom blocks and block macros are processed by associated BlockProcessors and BlockMacroProcessors, respectively.
- TreeProcessors are run on the abstract syntax tree.
- Conversion of the document begins, at which point inline markup is processed and converted. Custom inline macros are processed by associated InlineMacroProcessors.
- Postprocessors modify or replace the converted document.
- The output is written to the output stream.
Extensions may be registered globally using the Extensions.register method or added to a custom Registry instance and passed as an option to a single Asciidoctor processor.
Class methods
Create a new Registry, optionally with a block-based group.
Register an extension Group globally.
The group can be a Group subclass or an instance of a Group subclass.
Register an extension Group instance globally.
Nested types
- Asciidoctor::Extensions::BlockMacroProcessor
- Asciidoctor::Extensions::BlockProcessor
- Asciidoctor::Extensions::DocinfoProcessor
- Asciidoctor::Extensions::Extension
- Asciidoctor::Extensions::Group
- Asciidoctor::Extensions::IncludeProcessor
- Asciidoctor::Extensions::InlineMacroProcessor
- Asciidoctor::Extensions::MacroProcessor
- Asciidoctor::Extensions::Postprocessor
- Asciidoctor::Extensions::Preprocessor
- Asciidoctor::Extensions::Processor
- Asciidoctor::Extensions::ProcessorExtension
- Asciidoctor::Extensions::Registry
- Asciidoctor::Extensions::TreeProcessor