philipwindecker
commented
2 years ago The central idea is:
- Create an extension for Antora that can be activated through a page macro (thus allowing for both project with and without conversion to coexist in the same Antora environment)
- Optionally, also add a "autoconversion" configuration to the site.yml to support automatic conversion without the use of an on-page macro
- Add the macro to the respective page to mark it for conversion
- Use the existing ifdef logic for use-antora-rules to mark the parts that need to be converted
Create an extensions (activation: optional) that creates a nav.adoc from the main file of an Asciidoctor repository structure (a main.adoc or an index.adoc) and update the other (virtual) file before it is converted to an Antora page.
This would remove the need to manually manage the navigation file whenever the main file is updated whilst also keeping the options for both Antora and Asciidoctor open. It would also make the transition for existing Asciidoctdor projects easier.