Nikola VS pages-gem

Nikola is a feature-rich static site generator that supports a variety of formats for content creation, including reStructuredText, Markdown, and Jupyter Notebooks. It offers a flexible architecture, allowing you to use different template engines and supports plugins for extending functionality. Nikola is suitable for both simple blogs and complex websites.

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.

I tend to prefer static site generators for this kind of use case. I use Nikola, which is written in and based on Python. You should be able to pick whatever html5up template you like and turn it into a Nikola template, too.

I switched to Nikola recently: https://getnikola.com/

Reads every kind of plaintext format, but will also just publish a Jupyter notebook which means you can do drag and drop image and graph inlining which makes everything so much simpler (and thus makes me more likely to keep it up).

I've been using Nikola and am happy with it: https://github.com/getnikola/nikola

Might be this static site generator: https://getnikola.com/

Found it by searching [nikola software].

I know you say you're comfortable with your workflow, but just wanted to throw out that if you're not dependent on Jekyll, and are simply looking for the best way to create a static site/blog from org-mode files, you could consider Nikola as an alternative. It has an excellent org-mode plugin which would likely solve your complication.

I also know that there is also Python-based Lektor [2], however I found Nikola more intriguing than this one.

[0] https://getnikola.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.