ButterCMS, a headless CMS vendor, publishes posts on web development, React, microservices, flat-file CMSs, and Ruby gems.
HN commenters mostly mention ButterCMS as a product, with customers praising its Rails gem and non-technical users; its founder also comments. Its blog posts get linked occasionally.
Many of the comments suggest that of course you wouldn't use React for a blog.
Someone forgot to tell these folks:
https://buttercms.com/blog/how-to-create-a-blog-with-react/
https://www.sanity.io/guides/build-your-first-blog-using-react
(and many more)
I'm firmly in the camp that React and similar frameworks are overused. However, the point is that there's a large part of our industry that is bought-in (and in many cases, built businesses around) the concept of "React all the things" and it's encouraging to see push back.
We use butter [1] for that, and we're liking the product so far. The various nontechnical people (ceo, writers) have been fine with it. Butter build and distribute a gem that just drops into rails and displays your posts. You have to style it, but you get the erb files.
They do have some support for local caching, but investigating that is on my todo list.
One big upside of this design is seo: your blog isn't on blog.domain.com, but wherever you want it on your main site.
[1] https://buttercms.com/
My company makes a product for developers (https://buttercms.com) and we've had mixed results with newsletter sponsorships. There doesn't seem to be a predictable correlation between the newsletter size and the amount of clickthroughs or signups we get from them. Will your database help with this?
Depends what you're trying to build. Customers have good things to say about https://buttercms.com/
Founder of https://buttercms.com here – we should talk!