MiddleMan VS Copier

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. - Source: Hacker News / 8 months ago

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. Source: 11 months ago

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/. - Source: Hacker News / over 1 year ago

Thanks u/Draegan88, but what's Middleman got to do with app architecture & design/ERD/schema design? Source: over 1 year ago

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. Source: about 2 years ago

We're using git repositories for the templates and using commits to enable updates (i.e essentially rebasing) similar to how Copier and Hygen do it. Any conflicts where the team has modified templated files can be resolved using git diff/merge. Source: over 2 years ago