hugo-theme-cactus VS pages-gem

FYI, it's a Hugo site based on the Kaktus theme made by me. It is a fork of the Cactus theme.

After years of analysis paralysis of choosing the right stack for my blog, I picked up Hugo, the Cactus theme[0], stripped lot of useless (for me) stuff, made some changes, published a new theme[1].

It has been going amazing for me![2]

  0: https://github.com/monkeyWzr/hugo-theme-cactus

Download Cactus theme for Hugo

I am using hugo with cactus-theme for this website.

I wish I could take credit, but it's actually a theme for Hugo called Cactus (https://github.com/monkeyWzr/Hugo-theme-cactus). I made some modifications to it however.

I wish I was that good at design :).

The tool I used to make the page is a static site generator called Hugo. The theme I used is called Cactus (https://github.com/monkeyWzr/hugo-theme-cactus). I made some minor modifications, but I really liked the style when I saw it.

I use the [cactus theme](https://github.com/monkeyWzr/hugo-theme-cactus) and tweak it a little.

It's super easy to publish a static site like the resume with GitHub Pages. Just check out the docs.

GitHub Pages: Host your static websites directly from your GitHub repository.

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.

Ideal for open source projects, docs sites, and portfolios. GitHub Pages

Github Pages: Link to Github Pages

Once you have all the documentation worked out a place to host it will be necessary. Some documentation generation may have ties in with specific hosting sites. Read The Docs' support for Sphinx and other documentation tools is one example. GitHub pages can be useful for GitHub hosted projects as it integrates well with GitHub Actions CI/CD deployments.

If you use GitHub and need to host a static website, consider GitHub Pages. Free for one site Stored on a GitHub public respository Deploy via web interface, or Git 100GB/month free bandwidth

https://pages.github.com/ https://docs.github.com/en/pages https://docs.github.com/en/pages/quickstart https://docs.github.com/en/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll

There are plenty of other hosting options you could use instead, such as GitHub Pages.

Functionally github.io just presents whatever you throw into the repository as the root directory of a site, github themselves host a very good, basic outline of how to set up a site on github.io.