I’ve been down this path enough times that I built https://sitepress.cc/ https://sitepress.cc/, which lets you embed content in a rails app with features that a

I’ve been down this path enough times that I built https://sitepress.cc/ https://sitepress.cc/, which lets you embed content in a rails app with features that are present in Jekyll, Middleman, etc. like Frontmatter, site hierarchy traversal, etc. It keeps content as files in the app/content directory, but when it’s time to pull data in from the Rails app for SEO, it’s all right there in the Rails app. There’s no “Headless CMS” crap to jump through. For me, this is another way of keeping everything in a monolith, and which requires a lot less context switching. If I’m building a feature and I want to create marketing or support content for it, it’s all right there in the same repo. I just create the markdown files I need, commit them to the repo, and I’m don. The thought of switching between a static content site or something like Webflow just seems silly for a small team or project.