High Voltage VS Middleman

If you only need some static pages in your Rails app, I think you can use something simple like: https://github.com/thoughtbot/high_voltage.

Also not quite what you're lookin' for but throwing it out there anyway: https://github.com/thoughtbot/high_voltage

I've always used high voltage for static files. You can configure it to use top-level routes. It isn't a problem. Requests for assets don't even hit the Rails router.

Most of the Static Site Generators default to generating blog from markdown, which is not feasible for company websites etc. For such projects I like Middleman (https://middlemanapp.com) which provides layouts/partials and things like haml templates.

I've done similar with Middleman, and I'm 99% sure you could set this up with Pelican if you wanted. It sounds like the site generation workflow is the issue rather than the tool.

I use middleman[^1] + bulmaCSS + FontAwesome but host on github using the `github.io` domain and upload podcasts to "archive.org"[^2]. The reason I choose this setup is because I want the content to survive as much as possible, hence open source technology and "free & long lived" hosting were requirements.

[^1]: https://middlemanapp.com/

[^2]: https://archive.org/

Thanks u/Draegan88, but what's Middleman got to do with app architecture & design/ERD/schema design?

I came across Middleman but it's meant to work with Ruby not necessarily Rails, it's also a bit old although appears kept up to date.

A simple middleman app consumes the data and builds a static export that runs standalone (just HTML, CSS and some JS files). That gets FTP'd/released to the webserver.

Middleman

For my personal site, which is 10 years old, I use Middleman, and I deploy the site to S3/Cloudfront with s3_website. It works fine for now. If s3_website stops working, I'll move to Netlify probably.