jackrabbit-oak VS Gollum

Assuming that by Apache Oak you mean the Oak subproject of Apache Jackrabbit ( https://jackrabbit.apache.org/oak/ ), why would you consider it abandoned? Release 1.48.0 came out last week and it's been seeing steady activity throught the last years - https://github.com/apache/jackrabbit-oak/ .

I am a committer and PMC member in the project, so I may be biased.

Arguably something like ikiwiki or gollum is doing this. These are both wikis that use git as their backend 'database'. I happen to like wikis like this a lot better over wikis that store their data in mysql or some other traditional SQL backend.

Gollum is self-hosted and uses git for version control https://github.com/gollum/gollum

https://github.com/gollum/gollum ?

For something quick and easy consider https://github.com/gollum/gollum#markups which powers Github Wikis.

Note that multi-user auth is NOT supported out of the box however.

That seems something in the ballpark of my favorite wiki software:

https://github.com/gollum/gollum

Edit and view pages as a normal markdown wiki. But the backend is just a git repository of markdown files so you can also just use your text editor and git pull/push. Usable by any novice but with the ideal power user interface.

I'm currently using Gollum Wiki in this way. It reads from a git repository, formats the markdown files nicely, and has a limited editor that is useful in a pinch.

I use Gollum, it's very simple but fits my needs.

Gollum would be an excellent solution. It's a web interface to a directory of markdown (or other formats), backed by git. Easy to sync the plain text files on your own devices (e.g. Syncthing) while still having a public web interface for school/work computers.

Gollum could meet the need. Logseq might work as well; here's a potential guide to self-hosting.