itty-bitty VS pages-gem

Your link doesn't work. According to the GitHub repo, the actual address is https://itty.bitty.site. And a DNS lookup for that domain name shows that it's hosted by Netlify. So you could start by reading Netlify's documentation.

Similar to your interest. I've been experimenting with Data URIs and base64 encoded html pages. I could manage around 400kb in url, beyond which it wouldn't load in chrome and firefox.

itty bitty is a great tool to store stuff in urls with compression! http://itty.bitty.site/

A plugin for Feather Wiki to export to itty bitty would be awesome. I've personally did some experiments. I'll share the finding to the Feather Wiki author to give him an idea and also add an issue for a plug in request, so some hackers can work on it...

I've created an issue at itty bitty github some time ago so that wikis like tiddly wikis and feather wiki could be fully compatible:

https://github.com/alcor/itty-bitty/issues/70

There is also link to an example in that issue.

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.