Overhaul Manage Add-ons and Packages #1724
Conversation
- Create a new Diataxis explanation section, Conceptual guides. - Create a new section, Manage Plone, and pages for frontend and backend. - Move bits from manage-add-ons-packages.md into appropriate files
|
All done. Ready for review @davisagli. |
|
|
||
| (manage-add-ons-packages-and-processes-label)= | ||
| # Manage Plone backend |
There was a problem hiding this comment.
I think in the future it might make sense to split this into "configure the Plone backend" and "manage add-ons" chapters. But that can happen later, when we add more material.
There was a problem hiding this comment.
Agreed.
I assume "add-ons" would retain the same content.
I assume "configure" would be a new page and include a port of https://5.docs.plone.org/adapt-and-extend/config/index.html. I'm loathe to start on this, however, until we have automated screenshots. I have high hopes for every sprint, followed by disappointment. I need help to make this happen.
There was a problem hiding this comment.
Hmm, maybe. I was thinking of this as more the stuff you do outside of the Plone UI itself. It could be that too, but then we have to decide how to handle the Volto vs Classic divide for it.
There was a problem hiding this comment.
OK, that makes sense. I'd prefer to wait until we have automated screenshots before starting on any web UI stuff anyway.
Can you provide examples of what should go into "configure"? Dexterity content types? Other?
|
I'm merging this as it helps set the stage for other documentation in progress. |
Closes #1706
This is a WIP. I have a couple more pieces to move around, but I would appreciate feedback.
📚 Documentation preview 📚: https://plone6--1724.org.readthedocs.build/