Do You Need A Headless CMS? With Updates

Do you really need a headless CMS? And I wanted to give you a quick update on sanity from my last video! We'll also discuss Jam stack and using a headless cms.

-----☆-----☆-----☆-----☆-----☆-----☆-----☆-----☆-----☆-----☆

► LEARNING TO CODE? CHECK OUT THESE COURSES! (SOME ARE AFFILIATE)

► Wes Bos's Courses!

___

___

Links:

[igorleal]

Hi @Erik, thanks for you inputs in this matter.

I’m facing this dilemma right now. I need to build a highly custom e-commerce website for my client and I’m currently deciding between building my own platforms (with Nuxt and Lavarel basically) or finding generic stuff (Ecommerce CMS) and customizing to my needs.

What would you do ?

Cheers

[tomast]

Jesus man that 'Charisma on Command' recommendation hitting 93% is the biggest piece of news from this video lol

[Dearth]

Could you do a video on headless WordPress? It's still the CMS clients request the most.

[jasonwitt]

You can construct CMS to dynamically generate the pages on the front-end just like WordPress does. That way the marketing people never need to touch code. You can emulate all the content management features you find in these large CMS like WordPress. You can do basic page/post creation, user accounts, taxonomies, and even menus. You're only limited by how you setup the data structure in the CMS and how you consume the data on the front-end.

[divingonline]

Prismic CMS is amazing. The slice feature is awesome and the pricing is good.

[SeanGoresht]

10:30 -- good observation; I think a main use case for headless CMS is to preview client data and to separate the "app" data from the front-facing "product" website. In fact, you could just as well use headless Wordpress or any CMS to manage your data, but these platforms are not designed the same way as headless platforms, hence better performance and more lightweight. It may be worth noting that this is not a new concept persay; platforms like CouchDB have had this feature for many years, and the new Futon editor offers many of the same benefits that these headless CMS offer (including realtime), and boast years of support, making them battle-tested. Dealing with conflicts is hard, and out of the box, you can use some of these older headless CMS with very little configuration. But, like you suggest, maybe all of this is going too far, and that maybe a simple Express/Koa/vanilla nodejs server will suffice. Maybe we all just like shiny new things, and these headless CMS are just playtoys.

[oscarmejia]

Would love a video that splits the two main categories of headless cms: Git-based and Api-based.

As for the topic here, I think JamStack is the future, I can see how the motivation to go all in isn't here yet, but when AI/machine learning api services become a staple in all data ... and WP/Drupal/etc don't get there fast enough, jamstack going take over real quick. I'm seeing clients be more and more proactive in their data, and they're going want their data to be analyzed by machine learning algos. Marking teams going jump on that quick.

[constantinross]

Would love a video on Strapi together with Vue or maybe even Vue. Maybe also go over topics like deployment etc.

[НиколайСладкий-нк]

Great, let's try "strapi" and create a video about it, I think it will be cool ;-)

[BrunoMateusMG]

Been working lately with Drupal 8 as a CMS only, data transfered by GraphQL and frontend in NuxtJs. Really interesting for me. Contenta CMS is a headless version of Drupal, but haven't tried it yet. Also works nice with JSON:API

[rjbullock]

I’m not sold on headless at all. There seems as many problems it introduces as it solves.

[donwinston]

Headless CMSs are great for people who want more complicated, harder to maintain, and therefore more expensive web sites. For example, Drupal now has a headless ability. But if you do this you'll only be using half of Drupal! Every time you want to change or add something you have to hire a javascript programmer. A themer, content editor, or site builder won't be able to do anything. Drupal has ten times the site building capability as any of the CMSs you mentioned and it's free.

[tommylu]

The marketing page and the Web app should be separate so that if someone messes up the page on the CMS, it won't affect people that are already using the app.

[kumbackquatsta]

please do a video on a headless cms and progressive web apps

[victormendoza]

Way overkill IMO. LAMP all the way. I am still excited about it, but it's cool to look at it from afar.

[SayWhaaaaaaaaaaaaaaaaaaaaaaat]

Best is STRAPI but it uses Node.JS and it's PAIN in the ass to deploy or use in shared hostings.
PHP version would be Directus, but i also like CockPit. super fast, super light no stupid CLI to do things.
Wordpress is perfect too.

[SayWhaaaaaaaaaaaaaaaaaaaaaaat]

ALL PROJECTS THAT REQUIRES CLI IS GARBAGES.