Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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?