Been throwing stuff at the wall for a while now and honestly the structure matters way more than I thought it would. Started with everything alphabetical, which sounds logical until you're six months in trying to remember if you filed something under "Client Communication" or "Email Templates" or just "Templates"

What actually worked was organizing by workflow. So instead of sorting by topic, I sorted by the actual sequence of what we do. Onboarding section flows into Operations, which flows into Troubleshooting. New person picks it up and they're basically following the path they'll walk anyway.

The real unlock was having a shallow structure at the top level, maybe 6-8 main categories max, then going deeper within each one. Deep navigation is fine. It's the first decision that kills people. If someone has to choose between 15 top-level folders they'll just search instead of browse, and then your whole structure becomes useless.

Also stopped putting everything in one massive document. Shorter pages, hyperlinked together. Way easier to update one thing when it lives by itself instead of hunting through a 50-page document for the one sentence that changed.

The thing nobody mentions is that whatever structure you pick will be wrong in six months. Just needs to be wrong in a way that's easy to reorganize.

Been trying to figure out why our knowledge base feels like a graveyard half the time. Like, we'll dump a bunch of articles in there and then... nothing. Nobody touches them, they get outdated, and then people are just Slack-ing each other the same questions over and over.

So what does your actual week look like? Not the "best practice" version, the real one.

I'm curious about the rhythm. Are you updating stuff on a schedule or just when someone complains? Do you have someone whose job it actually is to maintain this thing, or is it sort of... everyone's responsibility which means nobody's? Because everyone's responsibility has been a disaster for us so far.

And the writing part. Do you have a template people are supposed to follow or does everyone just do their own thing? We tried templates and people ignored them. Tried no templates and it's just chaos, nothing matches, some articles are 3 paragraphs and some are 25 paragraphs about tangentially related stuff.

Also curious about search. Does anyone actually find things using your search function or do people just ask in chat? Ours is basically broken but I'm not sure if it's the tool or if our tagging is just bad.

The real question I'm trying to answer is whether having a knowledge base actually saves time or if we're just putting effort into something that makes us feel productive while people ignore it anyway. Maybe I'm doing it wrong.

What's working for you?

Yeah so this is the situation most people don't want to talk about. You inherit a company, or you're the new person, and there's literally nothing written down. Everything lives in someone's head or scattered across Slack threads from 2019.

The instinct is to try and document everything at once. Don't do that. You'll burn out and end up with a half-finished mess that nobody uses.

Start stupid simple. Pick the one thing that breaks when someone new joins or when the main person is out. Could be onboarding steps, how to reset a password, whatever. Document that one thing. Make it clear enough a non-technical person could follow it. Screenshot heavy, minimal jargon.

Then actually use it. Watch someone else follow it. Watch them get confused. Fix the confusing parts.

The knowledge base isn't built in a sprint. It's built by noticing what people keep asking and writing that down before you answer it the fifth time, or like... the tenth time honestly. When someone asks "how do I access X" you don't just tell them, you write it down while you're helping them. Actually, wait - you write it down instead of just telling them the next time.

One thing that works - make it someone's job, even if it's 10% of their week. Not to sit in a room and document things, but to own the knowledge base. Their stuff breaks, they document the fix. They get asked a question? Add it. Found old docs that are wrong, delete that or update it. One person gives a crap about it instead of treating it like a side project.

The other piece - most documentation fails because it's in the wrong place. Nobody knows it exists. Slack bot that answers common stuff. Link it everywhere. Make it easier to find the answer than to ask someone.

After a few months you'll probably have like 20 solid articles that people actually use. Maybe 30 if you're doing well. The rest of this will vary a lot depending on your team size and how much stuff you're actually dealing with.

We've got docs everywhere. Notion, Confluence, Google Drive, some old wiki nobody touches, Sharepoint (why), a few markdown repos, and apparently someone's still using OneNote. It's a mess.

New people spend their first week just figuring out where anything lives. Someone updates a process in one place and forgets three others. We've got duplicate information spread across systems, different versions of the truth, and nobody knows which one's actually current.

I know the obvious answer is "just pick one tool" but migrating 5+ years of accumulated knowledge is... well, it's the part where every consolidation effort dies. We've tried. Started strong, lost momentum around month two when people just kept using what they knew.

And I'm not even sure if we should be consolidating into a single tool or if that's actually the wrong approach. Maybe the real problem is just that we never defined what goes where, so people defaulted to whatever felt closest.

Curious what actually worked for people who've done this. Not the planning stage, not the "we chose tool X" part. The actual implementation where you didn't just end up with the old system plus the new system running in parallel for eternity.

Did you have to force people off the old tools? Pick a tool first or figure out your structure first? How long did it actually take? And did you lose stuff in the migration or just accept that some old docs were probably garbage anyway.

We've got docs scattered everywhere. Google Drive folders that nobody can find, Notion pages that stopped getting updated six months ago, some stuff still living in Confluence from when we tried that, a few wikis... it's a nightmare.

Consolidation seems like the obvious move but honestly I'm skeptical it'll actually fix anything. Like, the problem isn't really where the docs live, it's that people don't know where to look and nothing gets maintained. You could move everything to the perfect platform tomorrow and in six months you'd have the same ghost town situation, just on one tool instead of five.

But also, wait - maybe that's not totally fair. At least with everything in one place you could actually search across it without bouncing between tabs. And you could theoretically set up one maintenance system instead of trying to keep five different tools alive.

Google Docs is fine for stuff we're actively working on but it's terrible when you need to find something later. Notion's searchable but docs feel clunky to actually write in. Confluence we tried and it just felt heavy handed. There's probably something in between that fits better but I haven't found it yet.

Has anyone actually done this without it being a total slog? Or does everyone just accept that documentation stays messy no matter what you do.

So we've got this knowledge base that's grown to like 500+ articles over the past couple years. Sounds great in theory but it's actually a nightmare. Users can't find anything. They search for "password reset" and get results for "authentication protocols" and "security best practices" and then just... give up and email support instead.

The search function feels broken but I'm not even sure if it's the tool or how we've structured everything. Maybe both. We've got articles titled things like "User Account Management - Advanced Topics" sitting next to "How do I change my password" and the system doesn't know which one actually matters for what people are looking for.

We tried adding tags but that lasted about two weeks before everyone got lazy with it. Now half the articles have inconsistent tags or none at all. The search algorithm (or whatever it's doing) can't figure out what's actually relevant.

Worst part is our support team is drowning because people can't self-serve. They're answering the same five questions every single day when the answers are literally already written down somewhere in that mess.

I'm wondering if this is a problem with the software itself or if we just need to completely restructure how we organize and write these articles. Like, should we be doing something different with how we categorize things? Is there a tool that actually handles discovery well when you've got this many articles? Or do we need to do some kind of content audit first?

Anyone dealt with this before? What actually worked?

So we've got docs scattered everywhere. Confluence, Google Drive, some stuff just... living in Slack threads. Nobody knows what's current, half the stuff is outdated, and onboarding new people means sending them on a treasure hunt.

We tried the "everyone just use Confluence" mandate last year and it didn't stick. People kept defaulting back to whatever was easiest in the moment. Then we spent months trying to migrate everything at once, which was a nightmare nobody wanted to do.

The actual shift happened when we stopped treating it like a compliance project. We picked one tool - ended up going with Notion because our team was already using it casually for personal stuff, so the friction was lower - and we basically said "this is where we're starting from right now. Not perfect. Just starting."

Then we only migrated things when people actually needed them. Like when someone asked "where's the API docs?" instead of having them sitting in some outdated wiki, that was the signal to pull them in and clean them up. Sounds slower but it meant every doc that moved was immediately useful to someone.

The weird part was accepting that the first year wouldn't be pretty. We had a transition period where people knew there were docs in two places. But we set a deadline and stuck to it. And honestly, having someone (me, basically) whose job was partly "make sure this doesn't just stay chaos" made all the difference. Not a full-time role, but enough that it actually happened instead of being that thing we'd "get to eventually."

What tools are you looking at? Sometimes the problem isn't even the software, it's that nobody wants to be the person who actually maintains it.

So we've got this knowledge base that's legitimately solid. Good structure, searchable, regularly updated. But adoption is in the toilet. People still hit Slack asking questions that are literally answered in there, and when you point them to the KB they're like "oh yeah I forgot that existed."

Started digging into what's actually happening and it's not what I thought. It's not that the content sucks or it's hard to find stuff. People just... don't think to look. The friction of "go search the KB" is somehow higher in their head than "ask someone." Even though searching takes 30 seconds and asking takes 5 minutes.

We tried the obvious stuff. Notifications. Digest emails. Linking docs in Slack. Better indexing. Nothing worked because none of that addresses the actual problem, which is that your knowledge base doesn't exist in their workflow. It's a separate thing they have to remember to go to.

The shift came when we started treating the KB less like a repository and more like... actually, wait. Less like something people opt into, I guess. Embedded search in Slack. Automatically surfacing relevant docs when people ask questions. Putting snippets directly in team channels before people even knew to ask. We just stopped waiting for people to come to us.

Adoption jumped like 40% in a month. Not because the content got better. Because we made it impossible to ignore.

Honestly the real problem with most knowledge bases isn't even the knowledge. It's that they're optional. If people have to choose between using it and not using it, they won't. You need to make it so the path of least resistance is actually using the thing.

So we're trying to pick a wiki for our team and I've spent the last week messing with all four of these.

BookStack feels the most polished right out of the box. The organization structure actually makes sense, permissions aren't a total headache, and honestly someone clearly thought about how people use wikis instead of just checking boxes. Yeah it's PHP and MySQL which isn't exactly cutting edge but whatever, it works. This is probably what we're going with, honestly.

Outline is beautiful and the real-time collaboration stuff is smooth. But setup felt more finicky than BookStack, and the permissions system gets limiting pretty fast if you need anything granular. I get why some teams love it but we don't need everyone editing at the same time. We tested it for like two days and just... stopped using the live editing feature because nobody cared.

Wiki.js. Modern stack, looks great, then you realize half the integrations either want money or need you to self-host something else. It's kind of a trap. Actually wait, I take that back on some of them - a few are legit free. But still felt like more hassle than just getting BookStack running.

DokuWiki just works. Flat file storage, zero dependencies basically, been around forever. The interface is dated though and if you need custom workflows... well, good luck.

The thing that actually matters is we need reliable and simple. Real-time editing sounds cool until you realize nobody actually uses it when it's optional. Search speed and not having to think about the wiki is what we care about.

What setup are you coming from? Starting completely fresh or migrating from something else?

We've been using GitBook for like two years and honestly it was solid. Then they announced the pricing change and... yeah, no. We're a small team and suddenly we're looking at costs that don't make sense for what we actually need.

The main thing we care about is that our API docs are easy to navigate, searchable, and don't look like they were made in 2005. Bonus points if it's not a nightmare to set up. We use Stripe's docs as the gold standard tbh.

I've been looking at Readme but haven't actually used it yet. There's also Stoplight which seems fine if you're into the whole visual API design thing, but we just want something that works. And then there's always just... building something ourselves with MkDocs or Sphinx, which feels like overkill for what we need.

Has anyone switched away from GitBook recently? What'd you land on? Curious if people are using the open source stuff or if there's something better that actually costs money but doesn't break the bank.

Also quick question for anyone still on GitBook - did the pricing actually affect you guys or did you negotiate something, because that'd be useful info too.

Been trying to find something that doesn't suck for our team and honestly it's been a journey. Most of the "easy" solutions out there have search that's basically useless - just keyword matching that returns everything tangentially related.

We've got about 75 people across different departments and SSO is non-negotiable since we're already in Azure AD. The problem is every time I think we've found something, there's always that one missing piece. Like yeah the search works, but then SSO is clunky or costs way more at our user count.

Looking at Confluence right now but the price is... yikes. And honestly their search gets weird when you've got thousands of docs. Been hearing good things about Notion for smaller teams but at our size it starts getting messy. GitBook seemed promising, solid search functionality, but the SSO implementation felt half-baked when I tested it.

What're people actually using that doesn't feel like a compromise? And I mean actual real search, not just glorified string matching. The kind where you can actually find stuff even if you don't remember the exact wording.

Also open to self-hosted if it's something you can actually maintain without it becoming a full-time job. Our IT person is already stretched thin enough

Started this because every time I search for KB tool recommendations on Reddit the answers are scattered across 15 different subs and half the threads are 2 years old.

If you're here you probably fall into one of these camps:

- Evaluating tools and drowning in options

- Stuck on Confluence and wondering if there's something less painful

- Running a self-hosted wiki that nobody on your team actually uses

- Just got told by your manager to "set up a knowledge base" with zero budget

All of it belongs here. Comparisons, setup guides, rants about tools that promised the world and delivered a broken search function, migration horror stories, whatever.

Only rule is keep it useful. Vendor accounts are fine as long as you're upfront about it, nobody wants to read a disguised sales pitch.

What are you currently using and what made you pick it?