Skip to content
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

Page orders in Antora vs Confluence #18

Open
wfouche opened this issue Mar 19, 2024 · 3 comments
Open

Page orders in Antora vs Confluence #18

wfouche opened this issue Mar 19, 2024 · 3 comments
Labels
Pending answer Issue that is currently waiting for feedback from user

Comments

@wfouche
Copy link

wfouche commented Mar 19, 2024

An unresolved issue in confluence-publisher is being able to (easily) control the order in which Asciidoc pages are published to Confluence.

See confluence-publisher/confluence-publisher#10

Is this a nonissue in antora-confluence, given that Antora has a nav.adoc file which specifies the location and page order?

@PacoVK
Copy link
Owner

PacoVK commented Mar 19, 2024

@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?

@PacoVK PacoVK added the Pending answer Issue that is currently waiting for feedback from user label Apr 2, 2024
@superflo22
Copy link

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

@PacoVK
Copy link
Owner

PacoVK commented Jul 5, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Pending answer Issue that is currently waiting for feedback from user
Projects
None yet
Development

No branches or pull requests

3 participants