Git-based vs API-driven CMS

A compare and contrast of content management systems that are powered by Git, and content management systems that abstract away the traditional database-backed CMS behind an API.

Transcript

1. @chrisdmacrae © 2017 forestry.io forestry.io Git-backed vs API-driven CMS Choosing the right tool for the job
2. @chrisdmacrae © 2017 forestry.io forestry.io Chris Macrae www.forestry.io
3. @chrisdmacrae © 2017 forestry.io forestry.io Old vs New Traditional CMS vs Headless CMS The Headless CMS The Traditional CMS
4. @chrisdmacrae © 2017 forestry.io forestry.io Decouple Content Management from Production Environments
5. @chrisdmacrae © 2017 forestry.io forestry.io Vendor lock-in Poor performance Poor reliability Poor security Cost The Problem The Traditional Stack
6. @chrisdmacrae © 2017 forestry.io forestry.io Content Editors get a CMS at the cost of Developer Freedom
7. @chrisdmacrae © 2017 forestry.io forestry.io Vendor lock-in Poor performance Poor reliability Poor security Cost The Problem The Traditional Stack
8. @chrisdmacrae © 2017 forestry.io forestry.io Poor performance
9. @chrisdmacrae © 2017 forestry.io forestry.io Poor performance
10. @chrisdmacrae © 2017 forestry.io forestry.io Poor performance
11. @chrisdmacrae © 2017 forestry.io forestry.io Poor performance
12. @chrisdmacrae © 2017 forestry.io forestry.io Poor performance
13. @chrisdmacrae © 2017 forestry.io forestry.io Poor performance
14. @chrisdmacrae © 2017 forestry.io forestry.io Poor performance
15. @chrisdmacrae © 2017 forestry.io forestry.io The Problem The Traditional Stack Vendor lock-in Poor performance Poor reliability Poor security Cost
16. @chrisdmacrae © 2017 forestry.io forestry.io Poor reliability
17. @chrisdmacrae © 2017 forestry.io forestry.io Poor reliability
18. @chrisdmacrae © 2017 forestry.io forestry.io Poor reliability
19. @chrisdmacrae © 2017 forestry.io forestry.io The Problem The Traditional Stack Vendor lock-in Poor performance Poor reliability Poor security Cost
20. @chrisdmacrae © 2017 forestry.io forestry.io Poor security
21. @chrisdmacrae © 2017 forestry.io forestry.io —Ines Gutzmer, Equifax “Today [Equifax] announced a cybersecurity incident potentially impacting approximately 143 million U.S. consumers. Criminals exploited a U.S. website application vulnerability to gain access to Social Security numbers, birth dates, addresses and, in some instances, driver’s license numbers.” Poor security
22. @chrisdmacrae © 2017 forestry.io forestry.io The Problem The Traditional Stack Vendor lock-in Poor performance Poor reliability Poor security Cost
23. @chrisdmacrae © 2017 forestry.io forestry.io –Wordpress.com VIP “Prices for WordPress.com VIP Cloud Hosting 
 start at $5000 per month for up to 5 websites.
 Our Self-Hosted services start at $15k per year.” Cost
24. @chrisdmacrae © 2017 forestry.io forestry.io Managing this complicated stack isn’t easy Need deep knowledge of the browser, of management of servers, databases, caches CDNs, the CMS, and of backup automation, versioning and so much more…
25. @chrisdmacrae © 2017 forestry.io forestry.io No thanks!
26. @chrisdmacrae © 2017 forestry.io forestry.io So what do we do?
27. @chrisdmacrae © 2017 forestry.io forestry.io The Solution The Headless CMS & The JAM Stack
28. @chrisdmacrae © 2017 forestry.io forestry.io Git-backed CMS API-driven CMS The Solution The Headless CMS & The JAM Stack
29. @chrisdmacrae © 2017 forestry.io forestry.io The Solution The Headless CMS & The JAM Stack
30. @chrisdmacrae © 2017 forestry.io forestry.io The Solution The Headless CMS & The JAM Stack APIs Stripe, Intercom, Disqus… Pre-generated Markup HTML, JSON, RSS, XML Javascript Native, jQuery, React, Angular, Vue…
31. @chrisdmacrae © 2017 forestry.io forestry.io Git-backed vs API-driven The Headless CMS & The JAM Stack
32. @chrisdmacrae © 2017 forestry.io forestry.io Storage The Headless CMS & The JAM Stack
33. @chrisdmacrae © 2017 forestry.io forestry.io The Headless CMS & The JAM Stack site.com
34. @chrisdmacrae © 2017 forestry.io forestry.io The Headless CMS & The JAM Stack
35. @chrisdmacrae © 2017 forestry.io forestry.io Cognitive Load The Headless CMS & The JAM Stack
36. @chrisdmacrae © 2017 forestry.io forestry.io The Headless CMS & The JAM Stack Pull from Git Download dependencies Build site
37. @chrisdmacrae © 2017 forestry.io forestry.io The Headless CMS & The JAM Stack Pull from Git Download dependencies Build site Authenticate with API Pull in content
38. @chrisdmacrae © 2017 forestry.io forestry.io Intellectual Property The Headless CMS & The JAM Stack
39. @chrisdmacrae © 2017 forestry.io forestry.io Solving the old stack’s problems The Headless CMS & The JAM Stack
40. @chrisdmacrae © 2017 forestry.io forestry.io Decouple CMS, frontend code, and backend code Great performance Higher reliability Superior security The Solution The Headless CMS & The JAM Stack
41. @chrisdmacrae © 2017 forestry.io forestry.io Decouple CMS, frontend code, and backend code
42. @chrisdmacrae © 2017 forestry.io forestry.io Decouple CMS, frontend code, and backend code
43. @chrisdmacrae © 2017 forestry.io forestry.io Decouple CMS, frontend code, and backend code
44. @chrisdmacrae © 2017 forestry.io forestry.io Decouple CMS, frontend code, and backend code
45. @chrisdmacrae © 2017 forestry.io forestry.io Decouple CMS, frontend code, and backend code
46. @chrisdmacrae © 2017 forestry.io forestry.io The Solution The Headless CMS & The JAM Stack Decouple CMS, frontend code, and backend code Great performance Higher reliability Superior security
47. @chrisdmacrae © 2017 forestry.io forestry.io Great performance
48. @chrisdmacrae © 2017 forestry.io forestry.io Great performance
49. @chrisdmacrae © 2017 forestry.io forestry.io Great performance
50. @chrisdmacrae © 2017 forestry.io forestry.io The Solution The Headless CMS & The JAM Stack Decouple CMS, frontend code, and backend code Great performance Higher reliability Superior security
51. @chrisdmacrae © 2017 forestry.io forestry.io Higher reliability
52. @chrisdmacrae © 2017 forestry.io forestry.io The Solution The Headless Stack Decouple CMS, frontend code, and backend code Great performance Higher reliability Superior security
53. @chrisdmacrae © 2017 forestry.io forestry.io Secure CMS Bulletproof frontends Backend via APIs Distributed infrastructure Superior security
54. @chrisdmacrae © 2017 forestry.io forestry.io Superior security
55. @chrisdmacrae © 2017 forestry.io forestry.io Superior security
56. @chrisdmacrae © 2017 forestry.io forestry.io Superior security
57. @chrisdmacrae © 2017 forestry.io forestry.io Superior security
58. @chrisdmacrae © 2017 forestry.io forestry.io API-driven • Easy to use content with multiple frontends • Ideal for content that changes < 1 per minute • Roll your own CMS through API • Many choices Git-backed • No vendor lock-in • Devs & editors using same workflow • Automated backups/versioning • Simple setup Pros The Headless CMS & The JAM Stack
59. @chrisdmacrae © 2017 forestry.io forestry.io Git-backed • Harder to use content for multiple frontends • Not great for content that changes > 1 per minute • Limited options • Content queries can be limited depending on the CMS Cons API-driven • Usually comes with storage and API usage limits • Devs & editors using different workflow • Backups and versioning highly dependant on CMS • Less control over content model/formatting The Headless CMS & The JAM Stack
60. @chrisdmacrae © 2017 forestry.io forestry.io TL;DR The Headless CMS & The JAM Stack
61. @chrisdmacrae © 2017 forestry.io forestry.io Static Websites https://forestry.io How do we build these sites?
62. @chrisdmacrae © 2017 forestry.io forestry.io Static Websites https://forestry.io How do we build these sites? Git-backed SSG (Hugo) Dynamic User State w/ Session Cookies Hosted on CDN
63. @chrisdmacrae © 2017 forestry.io forestry.io Static eCommerce Website https://prettyflyfpv.com “The amount of work needed to make a [traditional] content-management system even remotely as optimized as a static generated site […] are frankly overkill for 90% of the small businesses out there.” How do we build these sites?
64. @chrisdmacrae © 2017 forestry.io forestry.io Static eCommerce Website https://prettyflyfpv.com “The amount of work needed to make a [traditional] content-management system even remotely as optimized as a static generated site […] are frankly overkill for 90% of the small businesses out there.” How do we build these sites? Git-backed SSG (Hugo) eCommerce via Snipcart Hosted on CDN
65. @chrisdmacrae © 2017 forestry.io forestry.io eCommerce Platform https://nastygal.com How do we build these sites?
66. @chrisdmacrae © 2017 forestry.io forestry.io eCommerce Platform https://nastygal.com How do we build these sites? API-driven SSG SPA Enhanced + Mobile Apps via REST
67. @chrisdmacrae © 2017 forestry.io forestry.io Multi-format Publishing http://www.getty.edu/publications/romanmosaics/ How do we build these sites?
68. @chrisdmacrae © 2017 forestry.io forestry.io Multi-format Publishing http://www.getty.edu/publications/romanmosaics/ How do we build these sites? Git-backed SSG (Middleman) Multiple outputs Hosted on CDN
69. @chrisdmacrae © 2017 forestry.io forestry.io Multi-platform Applications https://wework.com How do we build these sites?
70. @chrisdmacrae © 2017 forestry.io forestry.io Multi-platform Applications https://wework.com How do we build these sites? API-driven SPA + Mobile Apps via REST Rails Backend (API) Hosted on CDN
71. @chrisdmacrae © 2017 forestry.io forestry.io What do all of these sites have in common? How do we build these sites?
72. @chrisdmacrae © 2017 forestry.io forestry.io Choose right tool for the job How you use a tool, and how effectively it meets your specific needs is what matters.