Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Is Headless CMS the future of development

Is Headless CMS the future of development

A headless CMS is a content repository that can deliver content to any front-end or device via APIs.
When you separate your content repository “body” from its presentation layer “head,” it becomes a headless CMS.

A headless CMS enables you to use any programming language or framework because of its simplified architecture. A lot of CMSs out there actually host and manage secure APIs for you as well. This allows you to easily consume content from anywhere. Whether it’s via a smartphone, app, or even a serverless function, you can easily access content by just calling an API, making an HTTP request, no matter what the programming language is. James stresses that a micro-service architecture enables small little things to be able to do things and actually connect you to your content.

Blessing krofegha

June 19, 2020
Tweet

More Decks by Blessing krofegha

Other Decks in Programming

Transcript

  1. What is Traditional CMS? Traditional CMS allows users to create,

    edit and publish content. It couples the frontend and backend together.
  2. The problem with Traditional CMS? As digital products continue to

    evolve, so does the content we consume. A scalable, cross-platform content management system is crucial to ensuring a product’s growth velocity. Traditional CMS gives the comfort of having the content, the editing interface, templates and custom codes, in a single environment. But with the changes in this mobile era, that’s no longer enough. We need a new breed of CMS.
  3. Headless CMS: What? A headless CMS is a content repository

    which can deliver content to any front-end or device via APIs. When you separate your content repository “body” from its presentation layer “head,” it becomes a headless CMS.
  4. Headless CMS: Why? The backend is entirely separate from your

    front-end application. In fact, you can have many applications anywhere. It doesn’t matter where they are hosted. The back end means that the database holds all your content and then the add-in application is entirely abstracted away from the developer.
  5. Headless CMS: what to look out for? ➔ Ensure your

    editors can manage all aspects of pages (Name, SEO and Content) ➔ Ensure your editors can manage URL redirections somehow ➔ Ensure your editors can understand your content architecture
  6. Looking for an Headless CMS ? Try Agility ➔ Global

    content delivery networks ➔ Content infrastructure, management, and delivery ➔ Rich Text Editing Support ➔ Built-in Page Management ➔ URL Redirections and routing Management ➔ Embraces the JAMstack approach
  7. To check out Agility CMS 1. Goto Agilitycms.com 2. Press

    button “request a demo” 3. Fill up the form 4. In the "company" name use code "juneteenth" 5. 50% off will be given.