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.
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
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…
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
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
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?
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
chrisdmacrae
toridori_dev
oracle4engineer
fullkaiten
tenshoku_draft
kniino
asei
neuecc
bbqallstars
nssv
tohutohu
fujiwara3
sansantech
eileencodes
holman
stephaniewalter
chriscoyier
keathley
garrettdimon
jnunemaker
akosma
panda_program
pauljervisheath
geoffreycrofte
![@chrisdmacrae © 2017 forestry.io forestry.io —Ines Gutzmer, Equifax “Today [Equifax]](https://files.speakerdeck.com/presentations/4d312715f6574ed99b612964138e31a5/slide_20.jpg){kind=link}
