Git-based or API-driven CMS - Chris Macrae

[@dezpapp]

Starts with the meat around 16:51 if you're coming here for the title theme. Otherwise rocks.

[@dezpapp]

35:00 is the true TL;DR

[@mosesnandi]

Good talk. The Git Based ones looks appealing to me. You don't have to worry about both backup and storage. With monolithic CMS... it's like you don't own your site.

[@rajuhs3086]

Excellent presentation.. The Q nd A session also shed light on many factors.. anybody in 2021 still interested on Git Backed CMS. I need more info on same.

[@ExperienceCrafter]

The git-backed CMS is like the cool indie band of the CMS world. It's all about keeping things in-house, in your git repo. You're in control, and you've got a workflow that developers can vibe with. It's like having your cake and eating it too, but the cake is your code, and you're eating it... well, you get it. In the git-backed side I would like to suggest Contentrain 🤓.

[@felixhaberle9522]

Drupal is Headless ready, so it can do both with REST API and can provide the best of both worlds with GraphQl and React for example. You can even use it with Gatsby or other Static Site Generators build in with predefined Gatsby Drupal Plugins.

[@Stevenchustudio]

18:33 - Golden advice where he starts talking about "Cognitive Load" - Git-based CMS (forestry / netlify cms) is great for deploying to one format.. bc everything is stored as markdown. However if your content goes to multiple types of applications or devices, API-based is better for you. It requires a lot more setup, but the cloud-based CMS is like Contentful hosts all your data as JSON in one place, then is sent out to site, mobile app, smart watch, etc. If you're just doing a site, API-based may be overkill.

[@StevenThelinClassi]

Very elaborate presentation with a lot of exciting and thoughtful points!

[@NickEnchev]

All this talk about ownership, decoupling and avoiding vendor-lockin, but we can't tie it all together without paying a license to Forestry? The personal $0 license is a great way to start, but we can't really "self-host" this like with other CMS tools.

[@lcapocer]

Great presentation, thank you.

[@FranckMercado]

Excelent video, very informative! Wordpress can also be used as Headless CMS too, haven't investigated too much on their REST API thought. It'd be great to see something like Vue.js + WP ;)

[@emveeoh]

Really great presentation. Thank you!

[@jdvivar]

Hi! Kirby is not a traditional CMS (I think), it's a file based CMS. In our implementation in the company where I work, we use it as a git based CMS. However it's true that Forestry for instance, works out of the box with git and it looks like a great solution.

[@abhishekmondal889]

Very Insightful and crisp presentation

[@rssbasdf]

Very Informative Presentation, Thanks for Sharing

[@ericwilliam1697]

PrettyFlyFPV's eCommerce section no longer works. Is this a reflection of poor performance of eCommerce on Static Websites? Also, my Wappalyzer Chrome Extension only lists Hugo on the Home page. Is Hugo only good for the first impression landing page? Then transfer to a bootstrap page hosted somewhere else?

[@priyaranjan1733]

Explained beautifully 👌

[@Stevenchustudio]

agreed. one of the most Sharp and insightful discussions on Git vs API on youtube!

[@hooshawn]

It's a no brainer

[@spygang7425]

is it cash or cayshe

[@ighsight]

@ 1:42 sad when Joomla! can't get a shoutout any more. Who else misses Joomla! Yeah, me neither.

[@astronat6746]

good info, but soooo many uhhhss, it keeps throwing me off

[@evolutionxbox]

cayesh...

[@ChristopherPhillips]

Is this guy just a shill for Forestry?