minimal-mistakes VS Hugo

My starting point was the Minimal Mistakes theme. From there, I copied the theme repository and meticulously removed everything I didn't need. This left me with the bare essentials, allowing me to build OneFlow from the ground up, but with some basic styling and features already at hand, which Michael Rose (the creator of Minimal Mistakes) has masterfully created.

cf.: https://github.com/mmistakes/minimal-mistakes/issues/2361

https://www.vladsiv.com/

Recently started a personal blog. The plan is to blog about Data Science/Engineering and implementation of modern data solutions in scientific research.

The blog is hosted on GitHub pages using minimal mistakes theme [0] (which I had to customize a lot to suit my needs [1]).

[0]: https://mmistakes.github.io/minimal-mistakes/

Thank you! As for the fonts: I user Jekyll and minimal mistakes for this site, and I just looked it up to verify: By default the theme uses system fonts for all of the font stacks (serif, sans-serif, and monospace). This is done in part to provide a clean base for you to build off of and to improve performance since we aren’t loading any custom webfonts by default. See: here. So it might have to do with the system fonts that you currently have set.

Link to the repository: [https://github.com/mmistakes/minimal-mistakes]

At one point though I realized there is a scaling problem with my build minutes. I knew that golang has considerably faster builds and in my case the easy fix is swapping over to Hugo.

This blog is running on Hugo. It had previously been running on Jekyll. Both these SSGs ship with the ability to create excerpts from your markdown content in 1 line or thereabouts.

Hugo

Hugo is a popular static site generator specifically designed to create websites and documentation lightning-fast. Its minimalist approach, emphasis on speed, and ease of use have made it popular among developers, technical writers, and anybody looking to construct high-quality websites without the complexity of typical CMS platforms.

As per many other comments, it sounds like a static site generator like Hugo (https://gohugo.io/) or Jekyll (https://jekyllrb.com/), hosted on GitHub Pages (https://pages.github.com/) or GitLab Pages (https://about.gitlab.com/stages-devops-lifecycle/pages/), would be a good match. If you set up GitHub Actions or GitLab CI/CD to do the build and deploy (see e.g. https://gohugo.io/hosting-and-deployment/hosting-on-github/), your normal workflow will simply be to edit markdown and do a git push to make your changes live. There are a number of pre-built themes (e.g. https://themes.gohugo.io/) you can use, and these are realtively straightforward to tweak to your requirements.

Create the technical documentation of your project You can use any of the following options: * A wiki, like the ArchWiki that uses MediaWiki * Read the Docs, used by projects like Setuptools. Check Awesome Read the Docs for more examples. * Create a website * Create a blog, like the documentation of Blowfish, a theme for Hugo.

Doing this made me appreciate existing SSGs like Hugo and Next.js even more👏👏

I suggest hugo: https://gohugo.io/

Generates a completely static website from MD (and other formats) files; also handles themes (including a lot of them rendering well on mobile), and different types of content - posts, articles, etc. - depending on the theme.

It's open source and, being completely static, cheap as fuck to self host.