XWiki.org Documentation Reorganization (batch 3)

[vmassol]

@MichaelHamann

I meant extensions in the sense of non-bundled extensions, not core extensions. I agree that users shouldn’t care about core extensions, but I think users should have an easy way to click through all documentation for, e.g., change request. Also, as I wrote elsewhere, my proposal here is really to have one tree per extension group, so change request would have one tree, not several for the different technical extensions.

ok so for non-XS extensions, we indeed need to decide what we do for the navigation. What we have proposed is defined in batch2, in proposal 5:

@vmassol

We also want to separate the doc for XS from the doc for non-bundled-in-XS extensions:

• The doc for XS should be reached when clicking on the “Documentation” menu entry
• The doc for non-bundled-in-XS extensions should be reached when going to e.x.o.

In order to achieve this, we propose to:

• Introduce a new xproperty to the Doc XClass (see previous proposal 4) to mark if a doc page is for XS or for extensions non-bundled in XS (by adding a “bundled in xs” boolean xproperty)
• By default don’t show non-XS doc in the main wiki
• By default don’t show XS doc in exo (the LT/LD of extensions should filter out extensions bundled in XS by default)

Visually, the idea is to show if the current doc page concerns xs or a non-bundled-in-XS extension by adding the info on the line of the Likes and Tags, in the form of a pill. In the future, it would be nice to generalize the idea and have a pill with a link to the extension page on exo.