blog VS Hexo

Take blog project structure as an example, the document structure is as follows:

A lot of great suggestions here and some stuff I’ve never heard of before!

Throwing my own suggestion into the ring, as I was just looking into this last week.

I started setting up a blog using Hexo. It’s another Node based SSG that uses markdown and supports tags. It has a lot of neat plugins that people have developed, too.

I like it so far!

https://github.com/hexojs/hexo

In my case, the latter is not possible because this blog is a static site, generated via Hexo and hosted on GitHub. It simply lacks a modifiable active server component.

Hexo — best lightweight SSG

Previously I've used Nuxt2 and even sooner - hexo.io

To make their creation easier, numerous open-source static websites generators are available: Jekyll, Hugo, Gatsby, Hexo, etc. Most of the time, the content is managed through static (ideally Markdown) files or a Content API. Then, the generator requests the content, injects it in templates defined by the developer and generates a bunch of HTML files.

https://gohugo.io/ written in go, support md https://hexo.io/ written in node

Hexo's

I'm currently using Hexo, I write articles in markdown, commit them to a git repository and push them to Github. I then have a Github Action to bundle the static website and publish it on Github Pages, so I get free hosting 👌

There are also many alternatives for selecting Static-Side Generating blog framework such as Hexo, Gatsby, Next.js (more details here). We will pick Hexo as our framework because it is a fast, simple & powerful blog framework.

Some alternatives I'm considering learning instead of Gatsby are Jeckyll or Hexo.