This document discusses headless CMS architectures. A headless CMS separates the backend content management system from the delivery of the content. This allows the content to be delivered through various interfaces like websites, mobile apps, or other platforms through an API. The content is stored and managed in the CMS backend database but is delivered through these different interfaces rather than being tied to just the CMS interface.

1. Headless CMS
ft. WordPress

2. Hey! I’m Dreb
@drebbits — Web Engineer at 10up
WordPress Davao | Community Team at WordPress.org

3. “Headless”

4. CMS Architectures

5. CMS Architectures
Coupled CMS

6. Front-end
Server/Environment (CMS)
Backend
Database
CMS Architectures
Coupled CMS

7. CMS Architectures
Headless CMS

8. CMS Architectures
“Head optional”

9. CMS Architectures
Headless / Decoupled CMS
Server/Environment (CMS)

10. CMS Architectures
Headless / Decoupled CMS
Backend
Server/Environment (CMS)

11. CMS Architectures
Headless / Decoupled CMS
Backend
Server/Environment (CMS)
Database

12. CMS Architectures
Headless / Decoupled CMS
Backend
API
Server/Environment (CMS)
IoT
- Websites
- Mobile App
- Desktop/Native App
Database

13. It’s HeadLESS
but you get MORE

14. CMS Architectures
It’s Headless but you get More
Reactjs
CMS /
Backend
Vuejs
Angularjs
Vanilla JS

15. CMS Architectures
It’s Headless but you get More

16. CMS Architectures
It’s Headless but you get More
Phase 1:
Single page web app
only
Phase 2:
Mobile Application
Phase 3:
Desktop Application

18. $WordPress = (headless) $WordPress
REST API

24. WordPress is your blank canvas.
..

25. Thanks!
- Dreb