upvote
There's Tina CMS for editing files in Git, but honestly editing flat files is probably the least interesting or complicated part of an enterprise CMS, and IMO there's rarely a good reason to interact with files directly versus a database that publishes files.
reply
I ran git-based blogs for years and have gone back to CMS. The instant preview and the instant publishing really make it a lot more pleasant to work with it. With Git, my read-eval-print loop so to say was a minute which is just too long. Fixing a typo then takes 2 minutes.
reply
Now I'm imagining a static site editing tool that runs the exact same templates client-side to power an accurate preview that are then used by the static page build process.
reply
I am building _exactly_ this for my org for the past month, using Nuxt Content.

A "draft" is a row in a database with live preview. Users can click a button to make a checkpoint (git commit, by GitHub API, but they don't know that). When they click "publish", the PR for their draft is merged.

Writers in my team can use a nice Tiptap editor with custom components. I get the change management of git.

The API for reading content and editing drafts is also exposed over MCP meaning AI can collaborate in the authoring process from anywhere that can connect to MCP.

Loving it so far.

reply
Depends on the company level, on my line of business, what companies care about are headless CMS, with AI workflows, and oriented towards MACH.

Ah, and all of them have partnerships with Vercel, and possibly Netlify.

Sitecore, Contentful, Sanity, Storybrook,...

If anything, they killed the need for backend skills, you get a ready made SaaS, program interactions with AI, and if anything requires backend like logic, it is taken care by Vercel or Netlify functions.

reply
> and static sites are cheaper to run (especially in this era of badly coded scrapers flooding the internet)

Is that really such a problem for the average Joe? I'm running multiple blogs via a Rust CMS [1] on the cheapest Hetzner server, and have had no problems with the scrapers or load or anything. Have also gotten to the HN front page without issues talking about that you shouldn't put a site behind Cloudflare since most don't need it [2]. Now of course, for businesses or something who depend on the service to be online, it's different. But I'm talking about regular Joe's blog here.

[1]: https://github.com/rikhuijzer/fx

[2]: https://news.ycombinator.com/item?id=45965060

reply
I had to add a Cloudflare CAPTCHA to my blog's search feature, but that's because I have faceted search which is a worst case scenario for bad crawlers.
reply
deleted
reply
[dead]
reply