HEADLESS CMS 

CMS System that allows creation and modification of digital content. ● WordPress ● Drupal ● Ghost 

CMS ARCHITECTURE DB (content) Admin interface (content editor) Frontend 

PROBLEMS WITH REGULAR CMS ● Monolithic architecture ● lower performance ● Lower reliability ● More exposed to security vulnerabilities ● Higher cost 

HEADLESS CMS ● decouple CMS and frontend ● great performance (Frontend is static, no DB) ● higher reliability (distributed infrastructure) ● Better security (hide CMS behind firewall, infrastructure is distributed) 

THE “HEAD” PART ● Gatsby ● Jekyll ● Hugo ● GitBook ● Hexo ● Middleman ● Spike ● Wyam 

HEADLESS CMS KINDS ● Git-based ● API-based 

GIT-BASED CMS ● Netlify CMS ● Prose ● Jekyll ● Appernetic ● Forestry 

GIT-BASED CMS Pros: ● no vendor lock-in ● same workflow for devs and editors ● automated backup and versioning ● simple setup Cons: ● difficult to use for multiple frontends ● not great for content that changes frequently ● content queries are limited by CMS 

DEMO 

API-BASED CMS ● Strapi ● Contentful ● GraphCMS ● Cockpit ● Superdesk 

API-BASED CMS Pros: ● easy to use content with multiple frontends (web, mobile, etc.) ● ideal for content that’s changing frequently Cons: ● storage and API usage limits ● different workflows for devs and editors ● backups and versioning aren’t guaranteed, depends on CMS 

DEMO 

SUMMARY Use git-based CMS when: ● You build static-first websites ● Content that doesn’t change too often Use API-based CMS when: ● Content changes frequently ● You need to support multiple frontends Find more: https://headlesscms.org/ 

THANK YOU 

QUESTIONS