obsidian-github-publisher VS pages-gem

Obsidian GitHub Publisher (the plugin)

400€ per year on a personal blog? To each their own, I guess.

I host my blogs on GH pages or Netlify. Additionally, I dump the notes I want to share with the world on GH pages as well with the excellent Obsidian Github Publisher [0] Plugin. I don't really care about analytics for a personal blog though.

Works for me, and costs nothing.

[0]: https://github.com/ObsidianPublisher/obsidian-github-publish...

MkDocs with Obsidian Mkdocs? https://obsidian-publisher.netlify.app

Love it! I've played with hugo blogging 6 years ago and liked it, but hated picking a template and didn't want to learn go to figure out how to customize things. I saw a different MkDocs obsidian plugin: https://obsidian-publisher.netlify.app/

Here is the documentation page of the plugin, which also serves as a demo of a published vault using this plugin https://obsidian-publisher.netlify.app

This plugin will handle all of this for you: https://github.com/ObsidianPublisher/obsidian-github-publisher

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.