Gollum VS BookStack

I’ve settled on similar setup. One nice thing about is there many tools that can work on this type of note setup, so you are not locked into one tool.

Working Copy works decently well on iOS. Gollum [1] on desktop operating systems provides a web interface to the notes. For some shameless self-promotion, I’ve been hacking on a clone of Gollum called Smeagol [2]. It is written in Rust so it is quite a bit faster to install and run on some of my low powered systems than installing Gollum.

[1]: https://github.com/gollum/gollum

However, if you are using a gui, you can use vimwiki and gollum together. Gollum is a web wiki.

Take a look at gollum or wikimd

Check out the Gollum wiki.

Another advantage layers on the source control: many source code management services will render your markdown and give you a search interface. GitHub popularized it. But other hosts like Azure Devops and GitLab support this as well. You can make a relatively pleasant document management system on top of this.

You can even run this on your own computer without an internet connection. Working Copy on iOS supports. Gollum, originally created by Tom Preston-Werner, strives to be compatiable with GitHub's wiki feature [2]. For my part, I've been learning Rust by writing a clone of Gollum called Smeagol [3].

Though really the point of the original article is: all these tool don't matter. Your plain text files can live longer than any of particular tool and continue to be useful.

[1] https://workingcopyapp.com/

[2] https://github.com/gollum/gollum

[3] https://smeagol.dev/

I just spent some time looking at this. There's no reason you can't use Obsidian with git. Obsidian just saves md files in a basic folder structure. You can git init in the root of your Obsidian vault directory (.gitignore your .obsidian folder). There's even an "Obsidian Git" community plugin that does the git work for you.

To serve your md files as a traditional wiki in browsers, there's a git backed wiki named Gollum that also uses md files in a basic folder structure. https://github.com/gollum/gollum You can see where I'm going with this.

Gollum doesn't have user authentication or anything fancy, it just renders and edits md files. I tried it. There didn't seem to be a difference between Obsidian's and Gollum's markdown. When I committed my entire Obsidian vault to a git repo, I could still choose to have Gollum serve the entire vault, or just a subdirectory in the repo. I could also disable all editing in Gollum.

While Obsidian is working directly with the md files, Gollum doesn't update until I actually commit the changes. Obsidian is basically an IDE for my wiki now.

I was mostly satisfied with Joplin syncing to OneDrive prior to today's experiment. But now I think Obsidian + Git + Gollum deserves a closer look. It might be a bit overkill for my personal wiki, but it could work in a team setting if everyone works on the wiki like they would a normal git project.

(Gollum)[https://github.com/gollum/gollum] can do that but that's a wiki.

Depending on what you're attempting to do, there might be possibilities in using the logical theme system or maybe the visual theme system but it would probably take some real hackery.

I use BookStack in my organisation. It meets your requirements (a), (b) and partially (c). It supports LDAP but no Nextcloud integration.

After that, get an instance of bookstack going, set it up to authenticate against your domain, set it up right the FIRST time. And then start documenting everything as you go. Set up a GOOD structure for your documentation FIRST, do NOT do this after the fact, as you are likely to kick it like a can down the road constantly.

If you haven't already, take a look at BookStack.

BookStack - Long term note storage

For context on PDF export I referenced this github issue a few times: https://github.com/BookStackApp/BookStack/issues/3087

BookStack