paint-brush
Benefits of a Decoupled CMS Architectureby@carsoncgibbons
1,004 reads
1,004 reads

Benefits of a Decoupled CMS Architecture

by Carson GibbonsFebruary 3rd, 2017
Read on Terminal Reader
Read this story w/o Javascript
tldt arrow

Too Long; Didn't Read

The relationship between content and code is nearing an end. It’s time to break up. With new interactive experiences being provided to consumers through apps, the consumer-facing presentation layer is not as removed from the content editor layer as it used to be. Content Editors have more freedom to plan and manage content as it will appear to the end consumer than ever before.

People Mentioned

Mention Thumbnail

Companies Mentioned

Mention Thumbnail
Mention Thumbnail
featured image - Benefits of a Decoupled CMS Architecture
Carson Gibbons HackerNoon profile picture

The relationship between content and code is nearing an end. It’s time to break up. With new interactive experiences being provided to consumers through apps, the consumer-facing presentation layer is not as removed from the content editor layer as it used to be. Content Editors have more freedom to plan and manage content as it will appear to the end consumer than ever before.

Modern frameworks and programming languages allow for flexibility in the formation of your content management stack. We write about ours in The Cosmic Stack. The method by which content editors can layout their content without affecting the visual rendering of their HTML and CSS on the front end is called “decoupling”.

Decoupling content from code is accomplished via CMS API when delivered by Javascript’s little content nuggets: JSON (JavaScript Object Notation). JSON is a lightweight data-interchange format. It is easy for humans to read and write. It is easy for machines to parse and generate.

Traditional vs. Decoupled CMS Architecture

A traditional CMS system such as a WordPress puts all front end HTML / CSS into a box with the content management system and backend so that content editors can fulfill all their work within the box. This already sounds set up for failure doesn’t it? Why give the keys to the kingdom to the person responsible for only one or two items?

A CMS API can not only help with content publishing speed and ease, but also preserve the integrity of the application overall. Early decoupled systems still assumed the developer was working within PHP, which only solved half the problem as new modern frameworks and languages further promoted light-weight interactive touch points within applications.

One API, Multiple Applications

Cosmic JS has solved that problem. Cosmic JS is an API-first cloud-based content management platform that makes it easy to manage applications and content. The secret sauce with Cosmic JS is that it decouples content from code for a decoupled CMS experience, but the CMS API can plug into any internet-connected application, regardless of programming language.

The Content Delivery API allows you to write once, deliver everywhere. When the same API that feeds mobile applications is also feeding your website, developers’ time is saved and projects’ budgets are met.

Write Once, Deliver Everywhere

Cosmic JS not only delivers content globally to your applications, but can also host deployed applications, stores media and content, grants user permissions to content contributors and allows for advanced content distribution and team management through features such as Localization and Webhooks.

Edit, store, manage and deliver content globally with Cosmic JS. Take back control of your content by having it publish independently of your code. Decouple, and know that better things are ahead.

If you haven’t already, get started by Signing Up for Cosmic JS. If you have questions about the Cosmic JS API, please reach out to the founders on Twitter or Slack.

Carson Gibbons is the Co-Founder & CMO of Cosmic JS, an API-first Cloud-based Content Management Platform that decouples content from code, allowing devs to build slick apps and websites in any programming language they want.