Pelican VS pages-gem

In my experience, [Pelican](https://getpelican.com/) does a good job of allowing you to edit themes on all pages at once with its static page generator.

There are a lot of built in features designed more for blog-like websites, but I’ve found it pretty easy to make my personal website with it.

Pelican is a preferred option for Python developers.

There's also Pelican but I haven't used it and seeing as Github serves static pages I'd imagine it builds and deploys your page and is done with it.

I use Pelican (https://getpelican.com/) for my blog, which works decently for me. It is a static site generator written in Python.

But you probably won't learn much Python by using it (or Rust when using a generator written in it) since you probably won't need to change anything in it.

Surely a "local private wiki ... not web based ... on a desktop application" is not really a "wiki" at all, but rather a "static site generator" with a built-in "search". If that's what you want, there's a Python app called Pelican. Writing such an app from scratch isn't really a beginners project.

Pelican — best for Python developers

You can - you'd basically just create a python script that parses your HTML/CSS files and replaces strings with values from your YAML. However I wouldn't recommend that unless you're just using this as an opportunity to learn Python. If you want to standup a real site and you want to use python, I'd recommend a Python static site generator like Pelican or Nikola.

As you're familiar with Python, how about https://getpelican.com?

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.