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

I1557 djencks #5

Open
wants to merge 4 commits into
base: i1557
Choose a base branch
from
Open

I1557 djencks #5

wants to merge 4 commits into from

Conversation

djencks
Copy link

@djencks djencks commented Sep 11, 2020

  • Use @djencks/asciidoctor-antora-indexer to show extensions
  • Show use of (new) indexBlock processor to display the "list" of extensions as a repeating block rather than a table.
  • The main camel-website package.json needs to be updated to use v. 0.0.5 of the asciidoctor extension.

I added a capability to the indexer extension to generate "repeating template blocks", and demonstrate it on a "copy" of the extension index page. I've included the badges like on extension pages as well as the information in the table. Is the stable/preview info shown on the individual extension pages? Some reorganization of the information is clearly necessary, but I don't quite understand all the possible choices. There's also the idea of having separate "since" for JVM and Native.

I don't know if this block display is a good idea, but thought it would be worth considering. I like how the "on-this-page" TOC has the list of extensions. Either this or the original index page should be removed :-)

I don't understand how the styling on status is supposed to work: I don't see any effect from it.

The [[explicit id]] at the top of each page can be removed, as it doesn't get into the Antora generated page.

I think the numerous page-aliases mostly cause confusion: are they really necessary?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants