Confluence. It's not bad. It's not great either. Which is pretty much the best way to describe all Atlassian products. It's unbearable on slow or spotty internet connections. It's riddled with bugs (just the other day my spacebar literally stopped working in their edit view). The formatting gets in your way more than markdown, but at least not as much as something like OneNote. But, it's powerful. Like any Atlassian…
Ask HN: Which Wiki or internal documentation tools do you use?
31–40 of 77 posts
Re: Ask HN: Which Wiki or internal documentation tools do you use?
#32We are tech company, everyone can learn to use Markdown and Git.
Re: Ask HN: Which Wiki or internal documentation tools do you use?
#33Confluence. It's not bad. It's not great either. Which is pretty much the best way to describe all Atlassian products. It's unbearable on slow or spotty internet connections. It's riddled with bugs (just the other day my spacebar literally stopped working in their edit view). The formatting gets in your way more than markdown, but at least not as much as something like OneNote. But, it's powerful. Like any Atlassian…
Re: Ask HN: Which Wiki or internal documentation tools do you use?
#34Re: Ask HN: Which Wiki or internal documentation tools do you use?
#35Re: Ask HN: Which Wiki or internal documentation tools do you use?
#36The downside is that to get it running with a good set of extensions that optimizes it for enterprise use takes a bit of an effort.
The upside is that once you do, it becomes an incredibly powerful tool that most users adopt without complaint. It hits all the OPs requests for searchable, code snippets (with syntax highlighting), and hyperlinking. When you add the ability to store and reuse structured data (Cargo or Semantic MediaWiki) it really becomes powerful.
Others I've tried:
- SharePoint (this is so bad it pains me to mention it)
- Confluence (not bad, but lacks structured data and seems to be focused on serving smaller teams vs. an entire company)
- OneNote (great for personal use, not as great for teams, especially not great at tracking multi-user changes)
- EverNote (great for personal use, not as great for teams, especially not great at tracking multi-user changes)
- Salesforce Knowledge (Didn't get too deep, but seemed better for help desk answer queue than internal documentation)
Re: Ask HN: Which Wiki or internal documentation tools do you use?
#37Notion ( https://notion.so ) All in one workspace, combines, trello, airtable, evernote, and docs. Great embed support and awesome for small teams and personal use. It's a modern day commonplace book.
The only reason I gave up on Notion sometime last year was that it was mind-numbingly slow. Great product otherwise.
Despite those issues, I have fully switched over to Notion. Instead of trying to force some very specific workflow onto you, it just offers a great toolkit that you can use to manage your own work whichever way you like it.
I would prefer a native app over a web app, but I guess that's just the world that we live in today.
Re: Ask HN: Which Wiki or internal documentation tools do you use?
#38Using XWiki the following documentation architecture is attainable:
Re: Ask HN: Which Wiki or internal documentation tools do you use?
#39> Some basic requirements are: - searchable - code snippets - hyperlinking I think another requirement to add is diagramming. I think wiki-style diagramming would be a big help for programmers to better communicate ideas. I've used external tools like draw.io but the overhead for editing, downloading, and uploading I feel gets in the way. Sadly, we are on confluence but don't use the draw.io plugin [1]. Built-in supp…
Would probably work nice as a plugin for a wiki.