At last an article that analyses the situation beyond the hype, this is how we can grow better solutions for the future, by constructive critic.
Headless CMS can’t be the goal on its own. There are plenty of problems to be solved in content management to increase flexibility and agility. Being API-based is, however, a solid corner stone, a foundation for the future that allows unlimited extensibility.
Pretty much like when the IPhone was announced, critics have targeted its simplicity and lack of features (premature virtual keyboard and lack of a physical one, its battery consumption, its fragility). Look at the market now, completely transformed and big actors like Nokia are now unheard of!
We’re going into the same transformation in the CMS world. Back when we announced our product, we’ve said that there are plenty of challenges to be addressed, I am glad this article mentioned quite a few!
None of these shortcomings are actually inherent to the API-based foundation. They just didn’t get enough attention.
As of today, https://prismic.io addresses most of them, and our focus is to find innovative and brand new solutions to this era’s marketing and publishing challenges.
I'd be happy to give details on how we address preview, scheduling, link management, security, cache, and modern marketing challenges if you're interested. Please keep these articles coming.
Sadek Drobi, founder at prismic.io