just a friendly reminder to all the folks involved in this iniciative: Plone has today a small and mature community with very limited resources; so, again, festina lente or, as the great philosopher Dolly Parton used to say, I'm gonna hurry just, just as slow as I can…
a few things you may like to read, share and discus:
Tjeerd Brenninkmeijer, CMO and co-founder of Hippo, in 7 Web CMS Trends for 2016 and Beyond
Headless CMS’s are Yesterday’s Silo
2015 saw the resurgence of the “headless CMS” idea — the idea that today’s content management system is one that doesn’t handle how the content it manages looks and feels in display. It simply manages the raw, structured content in a single repository.
But just because it’s a new capability for some, doesn’t make it a new idea. Every capable enterprise WCMS has (or should have) this capability.
It's a false choice. One CMS should be able to handle both: headless (e.g., for mobile app development or delivering content through an API to third parties) and a delivery tier to quickly roll out new personalized web channels.
A headless CMS often acts as an extra CMS for an organization next to the original CMS, which will create a content silo. Some remove this silo by moving all content to the headless CMS and creating a 'new’ one-off delivery tier on top of the headless CMS, but this guarantees future headaches. The marketer will ask for personalization, experiments, actionable insights, template and component management, etc. features ... And the development team is stuck with the maintenance burden of custom software while keeping up with the speed of the WCM software market.
…
The biggest, most meaningful trend of 2016 is how organizations can focus on creating meaningful digital experiences for customers, and get off the hamster wheel of producing more and more content. From our experience, those that pay heed to these trends — and focus on solution models that help them focus more on the quality of their content — will be the ones that succeed in the coming year.
Boris Kraft, co-founder and Chief Visionary Officer of Magnolia International, in A Headless CMS Won't Solve All Your Woes:
Where Things Get Complicated with Headless CMS
Headless CMSs raise issues of security, as it’s difficult to define which users get which access, creating a risk of delivering confidential content to non-authorized users. Delivering multi-language content requires a lot of development work to re-implement this feature. And with the separation of content and delivery, editors no longer have a way to preview the content they want to publish.
Another issue is personalization. Once you decide to separate the content from delivery, you need to rewrite a full personalization content engine. In many cases, form builders are also on the server, so integrations with marketing automation and other tools are lost as CMSs no longer have the capability to build the forms dynamically.
Today’s Solution May Cause Tomorrow’s Problems
In many cases, a headless CMS can result in increased complexity for developers and marketing teams. Your job is to look beyond the immediate attraction and think about the future.
It’s Not ‘Headless or Nothing’
The problems arise when companies decide that headless is the answer to everything. There’s no reason why you shouldn’t get a CMS that allows you to handle both headless content and the delivery layer.
The most important thing is ensuring that you have the flexibility to face the future, knowing that it’s impossible to predict.
Ted Schadler and Mark Grannan, from Forrester Research, in The Rise Of The Headless Content Management System:
Warning: Headless Content Management Is For Do-It-Yourself Shops
If you decide not to buy a packaged solution, you can compose one by adding content authoring and workflow tools, using different delivery tiers for different touchpoints, and implementing new kinds of content analytics. you may also have to push the pause button on WySIWyG.
I think we need a marketing team to help us visualize the future of Plone beyond technology hypes.
good night, and good luck!