Headless CMS Is Killing the Buy vs. Build Decision
contentstack.com
Headless CMS Is Killing the Buy vs. Build Decision
1–10 of 50 posts
Re: Headless CMS Is Killing the Buy vs. Build Decision
#2(according to a headless CMS provider)
Re: Headless CMS Is Killing the Buy vs. Build Decision
#3(according to a headless CMS provider)
I don't have any data to prove my point, but I have the feeling that more and more companies and individuals are using static generators for their public blogs/marketing/ corporate websites!
Re: Headless CMS Is Killing the Buy vs. Build Decision
#4I just skimmed this article since it does seem like a bias post from a Headless CMS provider however almost all transitional CMSs that you can use/build also provide the features of a Headless CMS. WordPress has a REST API built in, Wagtail has an API built in via django-rest-framework. I'm sure if I looked almost every other CMS has solutions for this too.
The build vs buy decision is still straight forward. Does the headless CMS solution I'm buying provide all of the features my project will need with room to grow? Yes? Cool, why bother building it. No? Looks like I'm building my own on a "reliable framework" (tm) already used by hundreds of thousands of sites.
Re: Headless CMS Is Killing the Buy vs. Build Decision
#5SSG FTW!
- Cross platform
- Best performance
- Ultimate security - no database or server code
- Use awesome development tools for funky stuff
- Easy to migrate to another thing
- Easy to experiment with in development settings
- Have small services for dynamic stuff that can be sepparatelly developed (comments, profiles etc.)
Its good to see era of Joomla and friends is coming to an end.
Re: Headless CMS Is Killing the Buy vs. Build Decision
#6(according to a headless CMS provider)
My immediate reaction as well. Headless CMS seems like a good idea, but I would not want to outsource the core of my own business if I were in the content biz. And honestly, if it were that advantageous, there’s no good reason there can’t or shouldn’t be open source headless CMSes just as there were headful open source CMSes...
Re: Headless CMS Is Killing the Buy vs. Build Decision
#7What a poor quality article, it doesn't have any explanation what a headless CMS is.
Re: Headless CMS Is Killing the Buy vs. Build Decision
#8Keep in mind that many FOSS CMS's can also do headless. Drupal has very robust JSON:API support (as well as GraphQL through a contrib module), and WP has its own Rest API. Drupal also has a distribution specifically geared toward headless/decoupled: https://www.contentacms.org
Re: Headless CMS Is Killing the Buy vs. Build Decision
#9the price is nutts!
Re: Headless CMS Is Killing the Buy vs. Build Decision
#10(according to a headless CMS provider)
My immediate reaction as well. Headless CMS seems like a good idea, but I would not want to outsource the core of my own business if I were in the content biz. And honestly, if it were that advantageous, there’s no good reason there can’t or shouldn’t be open source headless CMSes just as there were headful open source CMSes...
Strapi[0], Cockpit[1], Directus[2], Ghost[3].
Just to name a few open source headless CMSs. There are a lot more where they come from. And you can always add a JSON or Graphql module to your wordpress, drupal, etc.
[0] https://strapi.io/ [1] https://getcockpit.com/ [2] https://directus.io/ [3] https://ghost.org/