Pelican VS poor-richard

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?

My own blog and portfolio site is hosted on github pages. Since I'm knowledgeable with web development, I use a static site generator, it's a software which generates your site pages for you on the fly based on pre-determined html/css structure and markdown posts. The setup exists in a single folder and all you have to do is push the generated html files to a github repo and the content becomes live on site! It's 100% static and hence 100% free, no PHP scripting or apache or whatsoever. Jekyll and Pelican are the most popular static site generators if you wish to go that route.

Pelican (anagram of the word calepin which means notebook in French) is what is called a Static Site Generator (SSG).

I've switched away from Vue to using Alpine.js, which makes it easier to combine backend templates with frontend ones, but here's the repo back when I was using Vue: https://github.com/spotlightpa/poor-richard/tree/eb816cac807...

src/entrypoints/donate.js defined a custom element, which was included on layouts/donate-page/single.html and layouts/partials/get-src.html conditionally included the Vue component either with Parcel's dev server in testing or precompiled files in production.

It's not very different from what you'd do in any not-JS web framework.