Some basic requirements are: - searchable - code snippets - hyperlinking
I know of a few tools and I've even worked at companies that use git repos with markdown. I'd love to hear everyone's thoughts.
1–10 of 77 posts
Some basic requirements are: - searchable - code snippets - hyperlinking
I know of a few tools and I've even worked at companies that use git repos with markdown. I'd love to hear everyone's thoughts.
We've tried to use MediaWiki and other fancy solutions (inc. O365's SharePoint/online OneNote) and desktop OneNote is the only one that stuck. We have .one files for each major topic with sections and pages within them. It is kind of a "low tech" solution, and maybe that is why it works. It gets out of the way, easy to backup, no downtime, etc.
Although Microsoft keeps threatening to discontinue the desktop version of OneNote.
Its not perfect (Boostnote really only supports local files) but it does mean our shared body of knowledge is versioned to what is in our repos. If someone makes large changes they can work on documentation while they are developing the change knowing that their docs are only released when their change is merged.
If Boostnote was aware of this workflow or allowed editing directly to remote repos it would be pretty much perfect.
Github markdown files for short project specific docs.
And Confluence for everything else including a few technical guidelines.