There is a slight issue, which was already existing in the previous doc: content categorisation.
It is very clear what Code Reference | ClassicPress Documentation will/does hold:
Everything related to Code!
It is also very clear what Plugin Guidelines | ClassicPress Documentation will/does hold:
Everything related to Plugins!
Now, User Guides | ClassicPress Documentation, is less clear.
IMO, this should hold only guides for users.
Stuff like this (previously in the “Use ClassicPress” section) should not appear in a User Guide:
https://docs.classicpress.net/user-guides/developing-classicpress/
https://docs.classicpress.net/user-guides/installing-with-composer/
https://docs.classicpress.net/user-guides/testing-classicpress/
https://docs.classicpress.net/user-guides/testing-classicpress-scenarios/
https://docs.classicpress.net/user-guides/security-page/
Those are Developer oriented IMO (and even, contributor oriented) details.
However, all Developers also use ClassicPress and thus are actual users. Just as well, a user might develop with ClassicPress.
What surely neither of the 2 groups do, is develop ClassicPress itself, those are contributors.
Thus, I am just not sure, if we should keep it as is (everything not Plugin, Theme or Code related, goes into User Guides, unless it is a contribution related thing, such as testing CP, developing CP, etc).
We can of course group the user guides into “Developer” and “Consumer” or whatever taxonomies.
The question is crucial because if we change it, we do have to change it now, or never
This because @James (and whoever is contributing actual code) sometimes links to these pages.
The links are now already broken because someone (Beda) changed them
Thus, we need to fix this up once and for all, this means, none of the links can change later anymore.
That is why I want community consensus on this, before I send James the updated list of redirects to do.
The big question thus:
Add a new CPT “Developer Guides” (which then will hold whatever is not a end user guide and produce a new permalink trunk developer-guides/
), or, keep current User Guide and create taxonomies therein, which will not influence the permalink.
For simplicity obviously keeping user guides is easier, but I bet, this will be complained in future as “messy” (even if we include taxonomies to filter, it might confuse the one or other user).