Headless CMS

Headless CMS

The overview of available CMS solutions

800c1a87c30c83ccc214e220b09e4def?s=128

Konstantin

May 16, 2018
Tweet

Transcript

  1. 4.

    PROBLEMS WITH REGULAR CMS • Monolithic architecture • lower performance

    • Lower reliability • More exposed to security vulnerabilities • Higher cost
  2. 5.

    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)
  3. 6.

    THE “HEAD” PART • Gatsby • Jekyll • Hugo •

    GitBook • Hexo • Middleman • Spike • Wyam
  4. 9.

    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
  5. 10.
  6. 12.

    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
  7. 13.
  8. 14.

    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/
  9. 15.
  10. 16.