I think that on the CMS can of worms, the intersection of Elixir developers and content website editors is tiny, because the community does not seem to standardize a CMS that is aligned with what editors expect today. (Well the Beacon initiative proves that I’ll soon be wrong !)
For example, Kirby is a great CMS both for editors and developers.
For developers :
It works without a database (you can put content in Git if you want to), is reasonably fast, offers a declarative DSL for structuring content types and compose them into page types, and is however you want it on the headless ↔ visible spectrum, both with an API or correct-ish programmatic access to data types. You can add new block types of course.
For editors :
The UI is uncluttered and tailor-made (with yaml) to editors needs. There’s nothing not useful in the dashboard and there’s no way to fiddle with settings that are not explicitely provided by the developers. The editing experience is modern (lists of blocks, possibly nested + structured content types)
So what’s the catch ? You probably guessed, it’s PHP.
Despite that, if I ever build a truly contentful website in Elixir again, I would use it for the content part. The pricing is great (99$ or 349$ one-time-fee). I would spend my developing time building business logic in Elixir and instantly have a month of headstart on the CMS part just by installing it.
You can even define all of the content types Elixir-side if you really want to, since the editor UI can be API-driven.
I know this is a bit of a hot take, but I have built a lot of CMSs from scratch for Elixir backends over the years. Their users like them because they were built for their specific needs and evolved with them.
But today there’s this strange “flat file” CMS that is made to be driven by other backends and can work headless… so I would offer me and my client a huge reduction in time by using it for the content part. You can even define blocks that talk to your Elixir API, that’s not a problem.
And this is the one I’m aware of. I’m sure there are ton of other modern and drivable/consumable CMSs out there that a competent team already maintain and update for me while I integrate them into a bigger system .
It seems that Beacon is going to fill that currently empty spot, and that would be a very great thing for the community. I would also evaluate it if I got that kind of project needing both Elixir and a public facing site again.