Hoping I can get some pointers in the right direction.
I have a classic Plone add-on that I'd like to enhance with Volto (or make "Volto-compatible").
I'm trying to sort out in my head how best to "re-implement" this system in Volto. Perhaps it would be more of an update to the interface and user experience rather than a "re-implementation".
The system is for managing the governance of committees. It has committee chairs and vice-chairs and permissions that vary by role. It relies heavily on Plone's infrastructure: custom content-types, custom roles, permissions, behaviors and browser views.
I expect to continue benefitting from the custom roles, permissions and workflow while providing a custom Volto interface on top of the system.
Based on my objective, these are the questions I'm pondering at the moment:
- Is it enough to focus on defining custom Volto views? I'm looking at the patterns used in the Volto Hands-on training guide 13. Content types Views – Volto Hands-On — Plone Training 2021 documentation
- Other than implementing Volto views for custom content-types, what else should be on my checklist? I really don't know what I don't know here
- Do event hooks that perform actions when something happens behave the same - I figure the answer is yes, since any interaction with the API would trigger the same kinds of events as interacting with classic Plone
- Some of our functionality is provided by portlets, what's the best way to reimplement that with Volto? The best bet seems to be Volto slots, need to learn a bit about them