Headless CMS has always had a great focus on developer experience, but with Headless CMS being more in the mainstream, what're your thoughts on how the editorial experience can improve for content and marketing teams? Anchor

With a traditional CMS, that content could only go to that template that was defined, but with a Headless CMS, the content is frontend agnostic and can be sent anywhere - like websites, landing pages, mobiles, digital displays, etc.įurthermore, a Headless CMS can also pull in content from anywhere, like an eCommerce solution, a CRM, a DAM, etc., and be combined with the created content to be rendered on the frontend, working as a 'Content Hub'. This means that content can be consumed by all devices natively, usually via JSON, and then rendered as that platform should, without the need for cumbersome adjustments or extensibility. What a Headless CMS does, is it takes that content element, isolates it from the frontend, and retains it as a 'content infrastructure', and distributes it via API. In the case of a traditional CMS, like WordPress, the content is restricted to the WordPress backend, and rendered on a browser via themes and plugins. Key takeaways from the conversation Anchor What is a Headless CMS and why's there so much noise around it lately? AnchorĪ Headless CMS is a content repository that decouples the backend and frontend. Get in touch with him via Twitter or LinkedIn. Kaya is an extremely active voice in the CMS and DXP community, having written several pieces of key content for CMSWire, and is very actively involved in the content community at large. Kaya is the founder of Wordify, a content implementation company that helps SaaS vendors define a content strategy, and deliver better content experiences.

Wordify login