I'm working on a small team and we thought it would be good to start a more in-depth discussion about running a single Plone site which uses both the Classic and Volto frontends to render different pages.
I think the argument for why this would be nice is basically:
- We have a large website which has been developed over many years. We have lots of custom templates and schema-based content types and we believe completely re-writing with Volto would be a huge undertaking that we have neither the time nor budget for.
- At the same time, we would greatly benefit from using volto to render certain pages. Our site's landing page, for instance, has serious performance problems. A smaller, more achievable project would be to migrate this page to Volto (with more pages to follow in time).
- The messages we see in the documentation strongly suggest that Volto is the future ("New projects should use Volto unless a important feature or add-on is stil..."). We need to keep developing new features our website, but we don't want to get split off from the larger Plone community. If there is no smooth migration path then are we creating more migration work with each new Classic template we add?
I think these points probably hold true for many other teams maintaining existing Plone sites. So for us the question becomes: How likely is it that running classic + volto will be supported better in the future? How can it be done now and what would make the process smoother?