Heimdall VS pages-gem

The control panel is called Homepage. I like it more than Heimdall. To manage Docker I use Portainer.

You don't need to use heimdall with docker. You just need a working web server with PHP then install it from source: https://github.com/linuxserver/Heimdall Instructions are in the readme.

I prefer using Heimdall

There is a 3.x branch, but it hasn't been touched in about a year. Contrast that to the 2.x branch which was updated within the last week. Seems maybe there isn't any development on the 3.x branch.

Fo example, Heimdall is a dashboard, a polygon validator node, and an Android firmware flasher. All of which are quite popular projects

Heimdall - A homepage for self-hosted applications (like 'Homepage', but for people who prefer to do the config in the application, rather than editing .yaml files)

There is a more straightforward solution if it's all just for internal links. Set up something like heimdal. https://github.com/linuxserver/Heimdall

Heimdall: A homelab dashboard linking to all my services

Dispute configure heimdall correctly for your domain? There is a github issue about this: https://github.com/linuxserver/Heimdall/issues/362

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.