This document introduces content management and content management systems. It discusses traditional coupled CMSs and introduces headless CMSs, which separate the content authoring from content delivery. Headless CMSs make content accessible via APIs for display on any platform. The document outlines benefits of headless CMSs like omni-channel experiences, team flexibility, front-end flexibility, and increased development speed. It categorizes headless CMSs as API-driven or git-based. Examples of headless CMS options are also provided.

1. Optimizing
Content
Management
with the
Headless CMS
https://bolajiayodeji.com
@iambolajiayo

3. Bolaji Ayodeji
Developer Advocate at Hashnode
JAMstack Developer and Technical Writer
In love with Docs && Web Engineering

4. For as long as humans
have been creating
content, we’ve been
searching for solutions
to manage it.

5. The need for content
management didn’t begin with
the World Wide Web, but
simply increased, when the
Web was born in the early
’90s.

7. Outline
Introduction to Content Management
Introduction to Content Management Systems
Traditional CMS (Coupled)
Headless CMS, the what?
Headless CMS, the why?
Categories of Headless CMS
Content as a Service (CaaS)
Headless CMS Options

8. Introduction to
Content Management

9. The "big four" of
content management
Digital asset
management
(DAM)
Records
management
(RM)
Web content
management
(WCM)
Enterprise content
management
(ECM)

10. Introduction to
Content Management
Systems

11. A content management application
(CMA)
A content delivery application
(CDA)

13. Traditional CMS
(Coupled)

14. Traditional content management
systems are “coupled”.
The (CMA) and (CDA) come together
in a single application.

16. Headless CMS, The
What?

17. A headless CMS, is a back-end only
content management system built
from the ground up as a content
repository that makes raw
structured content accessible via
APIs or the Git workflow for display
on any platform or device.

18. Headless’ lacks content presentation
functionality or frontend display.
You need additional technologies to serve
the “head.”

19. The content is created and edited in the
back-end, and the front-end takes
advantage of flexible and fast web
services and APIs to deliver the raw
content to any front-end design on any
device or channel.

23. Headless CMS, The
Why?

24. 1
Omni-channel
experiences
2
Team
flexibility

25. 3
Front end
flexibility
4
Structured
data

26. 5
Security and
Scalability
6
Simple
workflow

27. 7
Development
speed
8
Content
repository

28. Categories of
Headless CMS

29. API DRIVEN
With an API-driven
CMS, you make
changes on the CMS
and deliver these
contents to your
application’s front-end
with an intermediary
API (JSON or XML)

30. GIT BASED
With a git-based CMS
you make changes
using the Git workflow
in a repository service
like GitHub that then
triggers a new build of
your site and updates
content.

31. Git Based
Netlify CMS
Publii
Forestry
Hexo Admin
Jekyll Admin
Strapi
Contentful
GraphCMS
Cosmic
Sanity
API Driven

32. https://headlesscms.org

33. Content as a Service
(CaaS)

34. Google Trends: 2015 - 2020

35. Google Trends: 2019 - 2020

36. Today's modern CMS revolution is
driving up demand for more flexible,
scalable, customizable systems that
deliver the experience you want, and
your customers expect.

37. The future is headless

38. Thank you!
https://bolajiayodeji.com
Twitter: @iambolajiayo
Hashnode: @bolajiayodeji
GitHub: @bolajiayodeji