Middleman VS content

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.

Nuxt is an appealing framework to work with, partly because of its robust module ecosystem. Popular UI libraries, headless CMS tools, and databases can be easily integrated with a single line of code. Among other third-party modules, Nuxt Image, Nuxt Content, and Nuxt UI are some of the official modules developed by the Nuxt team.

For reference also in the space of 'website from markdown':

* https://content.nuxt.com/ - JS, SSG and SSR

If you want to continue using markdown, nuxt 3 has a module, Nuxt Content - https://nuxt.com/modules/content https://content.nuxtjs.org/

Nuxt Content is what you’re looking for.

Then I recalled about Content. It's a file-based Headless CMS which use files of extension .md, .yml, .csv and .json a data layer for the application. And its MDC syntax is cherry on top. So I came with a plan to use .json files to handle project data. Basically, I'll just create a projects section using Content, put my projects in .json files, use the Querying functionality of Content to fetch them and populate the Components as needed.

I would argue that using something like Nuxt/Content[0]is even simpler. I create a new markdown file in my website’s local repo, write the content and commit if it’s ready for publishing. No need for the FTP step and version control is build in.

This setup is also completely free since the content lives on GitHub and my static site on render.com (but any static site hosting will work).

And since it’s Nuxt based, it automatically also supports more advanced features such as tagging, advanced queries and filtering.

Can only recommend it!

0. https://content.nuxtjs.org