| So, I agree that I don't think a software project solves the problems the post starts out with. However, I wonder if the project can be used to solve other issues? For example, I think there's a spectrum of knowledge-base like solutions, but the middle of the spectrum is often poorly served: - wikipedia: global, canonical reference material. Is very good, and we almost all use it in some fashion. - confluence/notion/gh-wiki: team knowledge base. Often spotty, stale, neglected. - logseq/obsidian/org-mode: personal knowledge base, notes. Typically very idiosyncratic, sketchy, but can work very well for the people who put effort into it. What if a "federated wiki" was targeted at the team/personal level? I'm not saying this is Ibis in its present form, but imagine: - You keep your personal notes and knowledge store, in a way which is always implicitly contextualized against corresponding info (or lack of info) in the team knowledge store. - When you're noting something new, or modifying something, you always have an easy path to push your personal addition/edit to the shared store. - Ideally notes from everyone's work around or interaction with some X drives low-effort maintenance of the community reference of X. |
have a local repo of your own notes, a hosted repo serving as the communal ref. if you want to make updates, commit and push --, you can cherry pick the sections you want.
i recall seeing something like mediawiki (but it stored articles as plaintext) a while back, you could use that for a web-based portal too