18 Matching Annotations
  1. Mar 2022
  2. Jan 2022
  3. Sep 2021
  4. Jun 2021
  5. May 2021
    1. When you separate your content repository “body” from its presentation layer “head,” it becomes a headless CMS. What truly makes a headless CMS better than a traditional CMS is its content-first approach with full APIs to access and display content in any way desired.
  6. Jan 2021
  7. Oct 2020
    1. I am going to start getting serious about headless WordPress development for my new website at jimgroom.net, inspired by Tom Woodward’s talk for #HeyPresstoConf20

      A lot of the posts I make to my WordPress site are done in a headless manner using the Micropub spec and the Micropub plugin with a huge wealth of Micropub clients.

  8. May 2020
    1. A pure headless CMS is different, because it offers no front-end capabilities at all, giving you full control of your customer experience via APIs. The CMS typically provides content managers with a presentation and channel agnostic way of managing content. It requires a front-end development team to manage the rest with the frameworks and tools they prefer: The content can be loaded by external applications which handle the content delivery to the client, meaning that the content can be (re-)used by multiple applications and channels (web, mobile app, audio guides, IOT).
    1. There is some confusion around what makes a headless CMS truly “headless”, as vendors use the term somewhat loosely to label their decoupled or hybrid CMS systems. But a true headless CMS is one that was built from the ground up to be API-first, not a full monolith CMS with APIs attached afterwards.