GitHub - zadam/trilium: Build your personal knowledge base with Trilium Notes
github.com
Build your personal knowledge base with Trilium Notes - GitHub - zadam/trilium: Build your personal knowledge base with Trilium Notes

I mean Trilium is fantastic app, lots of potential but the developer is struggling on his own, maybe it’s because it’s younger than logseq or maybe because is open source compared to obsidian. I think it’s the best note-taking/knowledge-base/second-brain i know it virtually could link everything you posses toghter to create a gigantic wiki, so much potential. Plus it has its own self hostable syncing server and web app. Guys give it a look and tell me what you think

  • @hodgepodgehomonculus
    6•11 months ago

    Ive tried out loads of thees knowledge base apps, but I always end up coming back to org-mode and org-roam. Once I integrated everything into Emacs, its hard to swap out to something else.

      • @hodgepodgehomonculus
        1•11 months ago

        I have a pretty basic org-roam setup I think. I keep my org files all in a directory called “org” that I sync with syncthing (previously I used Dropbox), and whenever I setup a new machine, I just grab that folder and put it at my user root (with Dropbox I would just symlink the folder from “~/Dropbox/org” to “~/org”).

        Now no matter what machine I am on and where I make my changes I have them all up to date.

        I generally have large nodes that contain all my knowledge, and I split them up as they get too big. E.g I used to have a single UnityEngine node, but over time I have split it up into many different nodes: EditorWindow, ScriptableObjects/UnitTesting/etc…

        I have at least one node for each of my projects, and there is a “Tasklist” heading in each of those project nodes which contain all my TODOs, those project files are tagged with the name of the project, so that I can easily write an org-agenda search to grab all the TODOs from a single project into a single view without anything else I have stored in the file (which includes a project synopsis, architecture notes/UML diagrams, general notes, etcc…).

        Since I am already in emacs when I am writing code, this keep it very simple for me to have this information as accessible as all my code files are. When I discover a new language feature or have to look something up, I just open up the node for that language, and put that new information in, linking to the source where i grabbed that snippet, or where the full MSDN documentation is stored if I need to go more in depth that my short description I write it. Copying down the information helps me internalize it, and I can easily just search through that file for information I have stored. This means that even if I don’t have internet access, I have access to all my previously looked up information I maybe have forgotten.