quartz VS Lektor

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

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.

I haven't used it since forever ago, but Lektor [0] is this weird in between. You need to be able to pip install and run `lektor serve` in the terminal but most else is done in the browser.

[0] https://www.getlektor.com/

Guess I'm one of the annoying users who complained when armin's Lektor (https://github.com/lektor/lektor) started going dormant back when, but I loved it for a while. I'm on Astro now, but a big thanks for helping a younger version for me.

Lektor is a modern and flexible static content management system that utilizes Python as its core language. It comes with an intuitive web-based admin interface, making it easy for content creators to manage and update the site. Lektor supports a variety of content types and has an active community that contributes to its continuous improvement.

Lektor CMS is sort of a prototype-ish thing doing this: https://www.getlektor.com/

It has (used to have? Can't find them on the site now) pre-packaged binaries that you would drop into a folder structure generated by the technically-minded person, and the content editor can simply click on that binary, which opens the backend of the CMS in the web browser, make changes and click deploy.

There have been several Flask-based CMS's but I don't remember most of them. IIRC Lektor is based on Flask.

Static hosting could be enough for many sites and one could combine the technical and UX advantages of your dynamic interface with the advantages of static sites for security and distribution.

I found that useful when i worked with https://www.getlektor.com/ years ago. In lektor the dynamic part runs on a users desktop machine, but it of course wouldn't need to.