Live data from Hacker News

Ask HN: Which Wiki or internal documentation tools do you use?

news.ycombinator.com

41–50 of 77 posts

Re: Ask HN: Which Wiki or internal documentation tools do you use?

#41
post #25

Nuclino ( https://www.nuclino.com/ ) It's a minimalist wiki with markdown support and real-time collaboration features. A lot faster and more lightweight than most of the old school wikis e.g. Confluence, MediaWiki, SharePoint (ugh). Also has a kanban board view for sprint planning.

Thanks for mentioning us (I'm the CTO)! Let me know if you have more feedback or questions.

Re: Ask HN: Which Wiki or internal documentation tools do you use?

#42
post #31
post #18

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…

I just rolled out Confluence a couple of weeks ago after really struggling to find a better option. I looked at Quip but it felt more informal than I was comfortable in particularly the lack of ability to setup teams and permissions that way.

> I just rolled out Confluence a couple of weeks ago after really struggling to find a better option.

When you take into consideration price AND maturity AND feature set it's honestly hard to beat. I tried lots of open source Wikis and all of them lack significant amounts of polish and/or features. Confluence at least resembles a mature solution that mostly covers all the bases. And if you're a small (very small) business or just doing a personal/family Wiki, $10 per year for all that can't be beat.

Re: Ask HN: Which Wiki or internal documentation tools do you use?

#43
post #18

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…

If you want something similar to Dropbox Paper, but better optimized towards long-term documentation, you should give Nuclino (https://www.nuclino.com) a try. In terms of organization capabilities it is similar to Confluence. But I'm the CTO so I'm obviously biased.

Re: Ask HN: Which Wiki or internal documentation tools do you use?

#44
I'd be curious if anyone can summarize the tradeoffs between Confluence + MediaWiki at some point. From what I've seen it seems to come down to:

(1) MediaWiki is definitely more responsive (Confluence can be quite slow) and, importantly, considerably more expressive -- provide you can learn Markdown, which basically anyone can.

(2) But you're essentially stuck with email-based logins which can be a dealbreaker to some organizations (MW does support OAuth in theory, but only in theory it seems -- the setup seems to be basically not supported).

Re: Ask HN: Which Wiki or internal documentation tools do you use?

#45
I'll mention clubhouse.io every chance I get.

It's billed as a Project Management software (and it's great at that) but it can be great for documentation because it:

- provides hierarchical nesting (Milestones / Epics / Stories)

- each object can have a relationship to another (related, blocks, duplicates)

- each object offers a markdown text area, lists, github PR links/integration, comments, and can be moved between various stages (standard scrum stages or your own custom ones)

- each object can be assigned multiple owners, requesters, and followers

- each object can be tagged

- search by title, tag, owner, state, etc.

- each object can have files uploaded and attached

This allows me to track why the work was done, how the work was done, and what work was done, while providing a nice README as a comment.

Everything can be edited, or others in the team can leave their own comments.

It's odd for sure, but I love it.

Re: Ask HN: Which Wiki or internal documentation tools do you use?

#46
post #39
post #14

> 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…

Mermaid is a “Markdown for diagrams” that seems to use a more semantic markup instead of ASCII art: https://github.com/knsv/mermaid Would probably work nice as a plugin for a wiki.

I've been using Mermaid with MediaWiki and it has a lot of promise. Since Mermaid lets me generate diagrams from text and MediaWiki lets me store and modify structured data, I can have MediaWiki pass Mermaid data to generate graphs/diagrams that stay up-to-date as the wiki changes.

I would like to see Mermaid be able to group sibling nodes[0] though, once I can do that, I can autocreate really nice organizational charts :)

[0] https://github.com/knsv/mermaid/issues/637

Re: Ask HN: Which Wiki or internal documentation tools do you use?

#47
post #23
post #10

Notion ( 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.

It's gotten faster and is getting faster over time. It was much, much worse a year ago which makes me believe that the team is paying attention to speed.

Compared to the main competitor mentioned here - Confluence - it is blazing fast.

Re: Ask HN: Which Wiki or internal documentation tools do you use?

#48
My entire wiki lives on GitHub (https://github.com/nikitavoloboev/knowledge).

I then use GitBook to publish it on the web and have fancy features like search and contents table on the side.

https://wiki.nikitavoloboev.xyz

Been using this approach for over a year now and I love how seamless the workflow of updating files in Sublime Text, pushing it to GitHub and seeing it live is. At this point my entire knowledge base lives online and is referencible and I love it.

The way I approach updating the wiki is in the wiki too:

https://wiki.nikitavoloboev.xyz/other/wiki-workflow

Re: Ask HN: Which Wiki or internal documentation tools do you use?

#49
post #43
post #18

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…

If you want something similar to Dropbox Paper, but better optimized towards long-term documentation, you should give Nuclino ( https://www.nuclino.com ) a try. In terms of organization capabilities it is similar to Confluence. But I'm the CTO so I'm obviously biased.

Beautiful looking product. Any plans for a self-hosted version? Cloud based storage of a lot of information I deal with is a no go.

Re: Ask HN: Which Wiki or internal documentation tools do you use?

#50
post #10

Notion ( 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.

I loved their UI, but the incredibly horrible export to pdf or print drove me off it. I really needed pdf exports to release versioned documents.
Post reply on HN