We've built a new Headless CMS called Contento which is the only Headless CMS focused 100% on websites. This simple assumption makes a huge difference in terms of feature set, workflows, UI, product roadmap etc.
Pretty much all the others are omnichannel or "head agnostic" - after all the key point of Headless is that the content can be fed to multiple heads via an API. However, the benefits of Headless for websites is significant (even if you don't need to send content to multiple heads).
The Dev dependency for a Headless / Jamstack site build is high but based on several conversations we've had with agencies they are struggling a little. Moving from churning out traditional CMS based sites like WordPress to the more bespoke world of Headless seems a major jump that is throwing up lots of issues.
I'd welcome any thoughts as to how agencies looking to offer Headless CMS backed websites can do so more profitably (than currently seems to be the case)? All ideas/ thoughts welcomed. Thanks in advance.
PS For those not familiar with how a traditional CMS differs from a Headless CMS see the image below:
Top comments (0)