In my last blog, I talk about . As a refresher, a decoupled CMS architecture is one in which the front end application and the content management system are decoupled and function independently of one another. The Benefits of a Decoupled CMS Architecture Developers are more readily understanding that they can build slicks apps and websites without a locally installed content management system, and instead can go API-first to deliver content to more application destinations. Within the space, you’ll notice a few buzzwords that do have a striking difference in terms of application and use: Content Management API Decoupled vs. Headless. While both of these buzzwords insinuate that the CMS is separated from the management environment and that content is made available via API endpoint, the management and delivery of said content changes per buzzword. Headless vs. Decoupled A CMS is reactive — it manages content, then just sits and waits for some process to ask for it. Headless A CMS is proactive, preparing content for presentation and pushing it into the specified delivery environment of your application. A decoupled system concerns itself with what happens in the delivery environment. It usually has some concept of a templating system with editorial tools. Decoupled Content available via API Endpoint Reactively assumes content delivery being handled elsewhere Headless CMS Content available via API EndpointIntuitively concerns itself with delivery and presentation layer Decoupled CMS While both headless and decoupled CMS systems make content available via API endpoint, a decoupled system like takes it all a step further with the presentation layer of said content. Cosmic JS can manage content and users while storing media and making it readily available via API endpoint, but goes the extra mile of providing “forgiving delivery” so that content editors can plan, manage and deploy content, knowing that Cosmic JS will deliver the content as and will be globally devourable by any internet-connected device. Cosmic JS JSON is an that makes managing and building websites and applications faster and more intuitive. By , Cosmic JS empowers developer flexibility while ensuring content editors can plan and deploy content as it best suits them. If you haven’t already, get started by . If you have questions about the , please reach out to the founders on or . Cosmic JS API-first CMS decoupling content from code Signing Up Cosmic JS API Twitter Slack is the Co-Founder & CMO of , an API-first Cloud-based that decouples content from code, allowing devs to build slick apps and websites in any programming language they want. Carson Gibbons Cosmic JS Content Management Platform

Slack

Twitter

Build a GraphQL API-Powered Portfolio Website

Benefits of a Decoupled CMS Architecture

Follow me on Twitter

Read My Stories

Too Long; Didn't Read

Make resilience your competitive advantage

Headless vs. Decoupled CMS Architecture

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

How Virtual Socializing Saved My Mental Health

100 Days of AI Day 1: From Newsletter to Podcast, Leveraging AI for Audio Transformation

10 Threats to an Open API Ecosystem

10 Indications That You Should Invest in Automation Via APIs

10 Best Practices for Securing Your API

How Virtual Socializing Saved My Mental Health

100 Days of AI Day 1: From Newsletter to Podcast, Leveraging AI for Audio Transformation

10 Threats to an Open API Ecosystem

10 Indications That You Should Invest in Automation Via APIs

10 Best Practices for Securing Your API

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps