Which tool do you use for your internal wiki?
Hi, this might be discussed already (If it is, feel free to link me)
We are looking for an internal wiki. I have used Confluence which is great for an enterprise, but I am looking for a very early stage co.
We already use Github, Gitlab, and Trello. Looks like none of those have a wiki feature.
I see many of them here https://alternativeto.net/software/confluence/
Looking to here what the community is using. Thanks.
We use Notion for everything. Our "internal wiki' is just a Notion database set up as a simple list of pages. We try to keep it as flat as possible (as opposed to nesting pages) so everything's easy to find from the top level, although Notion's global search is pretty great and super fast nowadays. We also set the list to sort items from most to least recently updated, so the items people are working on the most are super easy to get to, as they're right at the top.
We use Notion as well, but have likely overloaded it. For example, I've been using it to create user stories and manage dev workflow in the kanban view. Notion is powerful enough to do this, but I've found it proliferates content and reduces the accessibility and value of other content. I'd love a Jira integration with Notion.
Thanks, Allen for sharing your set up.
Both GitHub and GitLab do have wikis, they are just bound to the repository. So for a company-wide wiki, I just create a separate repo. I do find the GitLab one to be a bit better, having features like search or outline. Effectively they are Git repos, so you can look through history or back them up somewhere else as well :)
I see. A separate repo for documents. Sounds fair.
I have seen the entire Gitlab co. itself is running using Gitlab. (I mean their documentation for on-call, maintenance planing everything).
This comment was deleted 4 years ago
I set up a wiki.js install in my company and we use that, it's very Dev focused and I don't think it's too user friendly when it comes to editing, but if the admins are technically sound then it's good.
It also uses a flat directory system rather than the usual one
I went through a fairly formal "here's what I need" and "here's what's available" process. I ended up going with WordPress of all things. It is:
I was sort of thinking "if in the future I want to do something different, what is extensible" and WordPress is one of the few where you can hire a developer and do pretty much anything you can imagine.
I also found 2 plugins that:
1.) Allow duplicating/templating entries.
2.) Regularly email updates to shareholders/stakeholders.
THIS. Awesome.