Open wfouche opened 6 months ago
@wfouche thanks for your issue, that is an interessting point. For now antora-confluence does not take nav.adoc
into account, because the output plugin only has access to the already converted .html
files. Hence, i need to investigate if i could get the infos from those HTML files. As of now antora-confluence per default defines the structure as described here
However, you can already make use of filters and mappers to easily control the output (using Confluence default ordering, which is in fact alphabetical). Maybe is that something that would already help?
As i understand so far mapping does not allow multiple pages in the same folder to be in a given order? It would just place all generatet Confluence pages under the target in alphabetical order, correct?
If not how should i specify my mapper so that Get started
is after Installation
?
├── antora.yml
└── modules
└── ROOT
└── pages
├── get-started.adoc
├── index.adoc
└── install.adoc
Hm, you are right. Since Captain not yet respects .nav files due to technical reasons, would it be possible to prefix the pages, eg:
├── antora.yml
└── modules
└── ROOT
└── pages
├── 03_get-started.adoc
├── 01_index.adoc
└── 02_install.adoc
That could work at least as workaround for now
An unresolved issue in confluence-publisher is being able to (easily) control the order in which Asciidoc pages are published to Confluence.
See https://github.com/confluence-publisher/confluence-publisher/issues/10
Is this a nonissue in antora-confluence, given that Antora has a nav.adoc file which specifies the location and page order?