You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Links of affected pages in Plone Documentation, if any.
overall nav structure
Description
Could we consider renaming "Frontend" and "Backend" in the navigation?
They are confusing misnomers. "Frontend" currently contains docs about Volto, but the Classic UI also has a frontend.
I propose that we:
change the title "Frontend" to "Volto UI"
move "Classic UI" so it appears immediately after "Volto UI"
"Backend" contains information about developing on Plone-the-framework, which for the most part is relevant to developers working on the Python portion of both Volto sites and Classic UI sites. I propose that we aim to move this content into the new Developer Guide which is started in #1731
@stevepiercy Let me know what you think. If this doesn't seem as obvious to you as it does to me, let's find a time to talk about it.
The text was updated successfully, but these errors were encountered:
In tonight's Volto Team meeting, we agreed with the two to-do checkbox items above. @sneridagh pointed out that it will also pave the way for the future "Bring your own UI" documentation.
Links of affected pages in Plone Documentation, if any.
Description
Could we consider renaming "Frontend" and "Backend" in the navigation?
They are confusing misnomers. "Frontend" currently contains docs about Volto, but the Classic UI also has a frontend.
I propose that we:
"Backend" contains information about developing on Plone-the-framework, which for the most part is relevant to developers working on the Python portion of both Volto sites and Classic UI sites. I propose that we aim to move this content into the new Developer Guide which is started in #1731
@stevepiercy Let me know what you think. If this doesn't seem as obvious to you as it does to me, let's find a time to talk about it.
The text was updated successfully, but these errors were encountered: