3 ms·
At my last job, we went from Drupal 7 to a headless CMS after evaluating several options. Our finalists included: Drupal 9: Would've been better, but it's a PI
by solardev 4y ago
At my last job, we went from Drupal 7 to a headless CMS after evaluating several options. Our finalists included:
Drupal 9: Would've been better, but it's a PITA to set up and maintain. It's also the second most-dreaded tech framework (behind only Angular) on the Stack survey: https://survey.stackoverflow.co/2022/#section-most-loved-dreaded-and-wanted-web-frameworks-and-technologies https://survey.stackoverflow.co/2022/#section-most-loved-dre... I will never use Drupal or work for a company that insists on it again.
Contentful, the industry giant, would not give us a quote without a NDA. In hindsight this turned out to be a blessing; we found much more suitable small businesses.
DatoCMS (who we ultimately chose): Really good dev support, small startup means their own devs/founders are very active in support and co-development. Good documentation and examples. Does everything that we need, great plugin support, good choice of fields and schemas. The editors and departments we tested this with, most of whom aren't techies, loved it. I enjoyed it a lot too, especially being able to hang out with the devs on their forums and Slack.
GraphCMS: Similar in many ways to DatoCMS but more powerful (writable/mutable GraphQL API), more extensible schema, better for devs but editors didn't like it as much. This IMO is the most "technically excellent" vendor-supported headless CMS and would've won my "dev's choice" award.
Other similar options: Grav, Sanity.io, Prismic.io, CosmicCMS, ButterCMS, TakeShape, Strapi, Storkyblok, Kontent, Ghost, Directus... here's a good list: https://www.cmswire.com/web-cms/13-headless-cmss-to-put-on-your-radar/ https://www.cmswire.com/web-cms/13-headless-cmss-to-put-on-y...
Airtable: Surprisingly capable with its REST API, for the super simple use cases. You'll have to handle permissions and caching yourself though (i.e. proxy the API through Cloudflare or similar). A really good way to get a simple website up and running.
Wordpress with ACF: You can turn off the built-in Wordpress-y-ness and just use ACF if that's better, but your client probably still wouldn't like it. Still waaaaaaaaaaay better than Drupal.
There are a bunch of open-source and/or self-hosted options, but IMO being able to move to a vendor-supported solution with built-in GraphQL endpoints was a DREAM. It meant being able to fully do a Jamstack with Next.js and Vercel or Gatsby/Netlify, and never having to touch the backend again.
Your client edits the content in someone else's CMS, you maintain the frontend, and it all just magically works with no infra maintenance... really frees up support.