Looking for a headless CMS for a personal/blog site as well as a way to give a bit of control to any clients that I hand a content-heavy site off to. Free and paid software are both an option. I am wondering if anyone has experience already with one that they’ve integrated with redwood, or if they have any on some sites that they personally reach for whenever the opportunity arises?
I recently heard about butterCMS on the JSJabber podcast earlier this week, but other than that I am clueless, so any direction is better than none!
I almost went down this rabbit hole myself a few months ago and found it very difficult just to get a straightforward comparison between the different options. I never ended up building anything but a lot of the research stuck in my head.
I quickly realized the question was hard cause when you ask the question “What CMS should I use,” a huge chunk of the responses you get just happen to be from developer advocates working at CMS companies. Crazy coincidence, right?
I eventually got a chance to ask a long time Jamstack community member about this and they broke it down for me in a way that’s stuck in my brain ever since, obviously this is a highly opinionated take:
I’ve been using (and company paying for) since late 2016.
What set it apart back in 2017ish and why we started paying, was fine grained team and role-based editing support as the content team grew (aka lots of interns) and only certain content models were allowed to be added edited and (rarely) deleted/archived.
Wow! I went from having nothing to having a few hours worth of research to do, I have to work on deploying my current project, but I’ll be sure to post my blog with whatever CMS I decide on over in the appropriate section! Thanks for the breakdown everyone
Thinking out loud here --> is there a scenario where it might make sense to connect to a Headless CMS via Redwood’s API? I naturally want to try and leverage the API where it makes sense, 'cause Cells(!), so I started mentally mapping out how something like that could/would work. But then I realized the whole point of a Headless CMS is not handling CRUD in your app, so no need.
It looks like this is what happened with @AryanJ-NYC when he did an experiment connecting to Sanity.io. I’m very curious about the Prisma parts and how they worked. And/or maybe he has a great idea to add support for Cells to be configured for other (additional) GraphQL endpoints.
Redwood Cells + Prerender support + Headless CMS == FTW (for a lot of people I think)