1. by Yves Do & Derrick Mehaffy - Meetup Zenika - December 12th 2018
The story of [headless] CMS
and why tomorrow’s content management will be headless
👔
👖
51. API-first or headless CMS let users manage content through a web UI.
Headless CMS allow developers to decouple content management from content rendering, as
opposite to monolithic coupled CMS (content is stored in a backend database AND rendered in
frontend templates using HTML/CSS).
Unlike a tradi6onal CMS, an API-first CMS exposes its content data via a consumable API.
Headless CMS are not concerned about how you choose to display content.
It pushes raw content (e.g. JSON or XML) for you to fetch and display anywhere.
tl;dr:
71. Case study
Derrick Mehaffy
@derrickmehaffy
9 Phoenix
Arizona
Head of Development Group
at Canonn Science & Research
Data Center OperaSons Technician
at QTS Data Centers
600+issues and PR commented on the
Strapi GitHub repository
72. Canonn is a community of about 6,000 players of the Elite Dangerous video game
that focus on researching and cataloging in game mysteries.
hbps://canonn.science