I am exploring options for a headless CMS for a community website where a non technical admin will post details about events in the community like a meeting or volunteering done by the community. They don't have funding. What is the cheapest option out there?
You're building something for a volunteer community, which means at some point you'll be gone and somebody will be wondering how the heck to manage the site with this "custom" setup that they can't figure out with chatgpt or a youtube video.
Set them up for the future, not for the now. WordPress. Just WordPress.
Reference: 26+ years in hosting, 4 years in WordPress-only hosting.
Wordpress, give them email and password, and a .pdf with screenshots on where to click to create a new post/page or edit stuff.
It required constant developer oversight, even when only publishing one or two articles a week. Things broke all the time. Builds broke constantly. Things went wrong left right and center.
Don't do it. Give them a Wordpress site.
Pros, a ton of docs, easy non-technical customization, long term support, many already experienced users, made for basically exactly what you're doing.
Cons, it's WordPress, and the actual wp-loop is a nightmare of bad choices.
Dead Comment
I don't think the LLMs change the argument either. If anything, dealing with the complexities of wordpress could make it even more difficult without someone who knows what they're doing.
Somewhere around 15 years ago, I thought wordpress was viable, but I think we need to leave it in the dust. I worked with it again 5 years ago, and the situation was no different from what I could tell.
Just set them up on a website builder like Webflow/Framer/Ycode/Squarespace/etc that has a CMS built in.
They complained about it constantly but they kept paying (7 years and going when I was doing work for them which by they way they constantly tried to shortchange me). Never feel bad about taking money from a company, its just business. Setup your income stream and take care of yourself. I'm not sure why there is this bizarre self sacrificing mentality in tech to make other people rich at your own expense.
Not to mention if you invoke those companies you are putting yourself in their walled garden that makes them money and takes control of your income away from you. Why would any person want to do that? There is no moral quandary here.
Buying into proprietary software and walled gardens is ridiculously common and acceptable in a business environment. That's code for "no liability if something goes wrong, minimal maintenance, and easy onboarding of new employees."
Even AI assisted it's going to be rough.
It's important to remember a vast majority of people have never used their desktop computer for more than MS Office and Google Chrome (facebook/youtube) and maybe ChatGPT now (still only 34% of the US population).
Heck, dealing with a file system is already too much complexity for most of the population.
Navigating around some enterprise-y headless CMS UI is already going to be a big ask. If these volunteers are anything like the ones I've dealt with before, they're going to struggle to even get past basic auth (which email did I use? What's my password again? What the hells a password manager???)
Though given that the psychopath alleged-incestuous-rapist Sam Altman has been the top user on the site since literally day one I suppose I shouldn’t be surprised
I've used it alongside Astro for both my personal blog[2] and two company sites[3][4]. It's worked amazingly well each time.
[1] https://keystatic.com/
[2] https://github.com/skeptrunedev/personal-site
[3] https://github.com/devflowinc/trieve/tree/main/website
[4] https://github.com/patroninc/patron/tree/main/website
Other Headless CMS felt restrictive, with shared drafts or the requirement for all published items to have changes go live instantly.
Once you're set up with your schema, the UI is easy enough for non-developers (and you can customize it for them if needed).
Headless is for sharing a common backend between a web site and phone apps. If you don't have the resources for the apps then it serves little purpose.
Or build/add an API when needed
We are sticking with it for now because it’s indeed good enough and I haven’t found any better options (give the price).
"Strapi applications are not meant to be connected to a pre-existing database, not created by a Strapi application, nor connected to a Strapi v3 database. The Strapi team will not support such attempts. Attempting to connect to an unsupported database may, and most likely will, result in lost data."
Unfortunately, most of the time I do not have such luxury. What are the CMS options for pre-existing databases?
Can you run some migration scripts to port the old database content into a new CMS?
Basically it provides a UI and all changes are pushed to GitHub which will launch the release process back in Netlify.
Seems it might fit your requirements too.
0. https://decapcms.org/
One downside for this setup, is that uploaded media are not re-sized or compressed (since there is no backend job doing it), so a client must be briefed into "making smaller images" (on the web client side with squoosh.app[2] for example), or using a SSG that does that built-in (hugo, gatsby)
0. https://github.com/sveltia
1. https://decapcms.org/docs/gitlab-backend/#client-side-pkce-a...
2. https://squoosh.app
https://www.gatsbyjs.com/docs/glossary/headless-wordpress/