OneNoteExporterAkaPublisher VS Gollum

A while ago I wrote a OneNote to whatever exporter (https://github.com/projectje/OneNoteExporterAkaPublisher), this can publish e.g. onenote to a md directory e.g. to be used in Obsidian.

I scripted some stuff like mass export ( https://github.com/projectje/OneNoteExporterAkaPublisher ) but did use the com api.

Adjust this powershell script: https://github.com/projectje/OneNoteExporterAkaPublisher to only export the Tags of type To Do or whatever is called.

When you have a family. A wife who barely knows how to create bookmarks in a browser and kids who only use their phone you need something extremely simple.

So you need to " scale " from 1 person to a household and take into account that all information you put in there, financials, recipes, addresses, etc. etc.. need to be ubersimple, working on a phone, auto sync etc... and need to continue working even when something would happens to yourself.

So that is why i standardized the knowledge management system in our household on OneNote (2016 client for the laptop).

This is because everyone understands office.

The API both the COM and the graph API also lets you create , update, read, etc... so you can write basically everything you can think of e.g. auto put bank transaction on the correct place in the correct table in the correct place in the taxonomy.

Thinking about the structure of a family and everything in there is also interesting and I had some larger revisions on that.

See also: https://github.com/projectje/OneNoteExporterAkaPublisher

Restructured a fork https://github.com/projectje/OneNoteExporterAkaPublisher still lots of #todos

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.