10 ms·
> A markdown driven wiki with Git This is exactly what I do. Though lately I've been transitioning to org-mode for non-personal notes as I don't need them on m
by dotancohen 5y ago
> A markdown driven wiki with Git
This is exactly what I do. Though lately I've been transitioning to org-mode for non-personal notes as I don't need them on mobile.
Your users can use any Markdown editor that they like. But one person should be responsible for creating new documents, so that there will be consistency in naming and placing in the hierarchy. Naming things is hard, leave that part up to the Knowledge Base owner.
- mplanchard 5y agoOn iOS, PlainOrg and BeOrg do a good job of making your org notes readable, searchable, and (basically) editable. I have heard there are good apps for Android as well, but I can’t vouch for them personally.
- xenodium 5y agoHey, nice surprise to see Plain Org mentioned (author here). Glad you find it useful.
- mplanchard 5y agoI’ve been using it since beta! It’s a great app, and I’m grateful to you for making it!
- denton-scratch 5y ago> leave that part up to the Knowledge Base owner. Well, that's against the philosophy of a wiki. Also, in a small team, nobody is the "knowledgebase owner" - he's just another developer. Putting a human in the workflow creates friction. But I'm totally with you on the "naming things" problem. A full-blown corporate knowledge management system is a repository you can throw anything into - invoices, emails, memos, reports, etc.; the system will automatically generate a knowledge taxonomy and article summaries. But such systems require much more maintenance effort than something simple like a wiki, and are overkill for a small team of developers.
- kaycebasques 5y agoOne lesson learned from leading https://web.dev https://web.dev is that a lot of people, even technical ones, aren't comfortable with git + Markdown. And then there are people who are comfortable with it but feel that it's too much friction for simple docs updates.
- dotancohen 5y agoFor those who are uncomfortable with Git: My personal git notes repo has this script right there in the document root: $ cat ~/Notes/sync.sh #!/usr/bin/env bash git add * git commit -am "$(hostname)" git pull git push echo '' git status That's good for 99% of my own use - and I'm a technical user. You can leave those last two lines off and redirect stdout to /dev/null. If there's an error on "sync" the user can call you over to handle what will likely be either a merge conflict or a network issue. Even for Windows users you can probably wrap that in a .bat file to be double-clicked on the desktop. And there are a ton of WYSIWYG Markdown editors. I've used Typora in the past.