quartz VS Jekyll

As others have pointed out you don't "host" Obsidian - it's just a local collection of markdown files. But if you're asking about a self-hosted alternative to "Obsidian Publish" for creating a knowledgebase that others can answer, I'm Quartz[0], a static-site generator designed to turn Obsidian markdown files into a website. I'm building and it and hosting it on Gitlab Pages at work[1].

[0]: https://quartz.jzhao.xyz/

[1]: https://quartz.jzhao.xyz/hosting#gitlab-pages

I wonder if https://github.com/jackyzha0/quartz was considered for this, though that project is more setup as an open source Obsidian publish replacement than a private PKMS

Shout out to Quartz, which produces a site similar to Obsidian Publish: https://quartz.jzhao.xyz/

(I would use Obsidian Publish, but it rendered far too slowly on some pages. I do use their excellent sync service though.)

https://quartz.jzhao.xyz/ + cloudflare, write in obsidian and publish with a git push

Quartz Docs

Jekyll is one of the oldest and most established static site generators. It’s tightly integrated with GitHub Pages, making deployment super easy.

I wanted to automate this boring and repetitive workflow: my idea is that every time a YouTube video is published on my channel I want to have an associated post on my personal Jekyll blog.

The static site generator (SSG) landscape is crowded with feature-rich but increasingly complex solutions. As I looked at and used tools like lume, 11ty, lektor, or jekyll, I found myself drowning in configuration options, plugins, and middleware. What started as a simple desire to convert Markdown content into HTML had evolved into learning complex frameworks with steep learning curves.

Jekyll

If you don't want to use Jekyll as your static site generator for GitHub Pages and you want to have a custom domain for your GitHub Pages. This post is for you!

Jekyll is a static site generator that transforms Markdown files into a fully functional website. Everything is generated into plain HTML, which makes it simple to deploy on platforms like GitHub Pages.

Obviously, there are a dozen choices for generating static websites (efficiently and quickly), from the classic Jekyll to the new Next.js. And you are good to go with any of them as long as your confident with it. I choose 11ty because:

That would be an improvement, but it still wouldn't be equivalent to what you can do with Ruby and Jekyll. For example I do [1] so I don't need to put dates in my post names, which also fixes a bug [2] I encountered but was never fixed.

[1]: https://stackoverflow.com/a/68287682/660921

[2]: https://github.com/jekyll/jekyll/issues/8707