问HN：你们如何防止文档变成部落知识？
我以前遇到过这样的情况：我加入一个团队后，某个人开始帮助我解决问题，然后另一个人过来告诉我：“哦，我们有一个文档页面，内容在这里。”
或者是另一种类似的情况：我开始尝试解决一个问题，搜索团队的文档却一无所获，但随后有人指给我一份正是我所需要的文档。真让人无奈。
这有点好笑，我所在的团队拥有丰富的信息，记录了所有内容，但几乎没有用，因为我在需要的时候找不到所需的信息，只有在这里工作了15年的乔知道一切是如何安排的，并且知道该指引我去哪里。我该如何避免这种情况？我该如何构建我的文档，使其易于导航，并且容易找到所需的信息。我难道不是唯一遇到这个问题的人吗？
从更高的层面来看，我意识到这个问题实际上是：“如何构建文档结构才是最好的方式？”
另外，有没有关于如何在Confluence中做到这一点的建议？我觉得至少有20%的问题是由于在这个工具中创建任何可导航的内容是多么糟糕。
查看原文
I've run into this situation before where I join a team and person X begins helping me with something, then person Y comes along and says, "Oh yeah we have a documentation page for this, it's buried here."<p>Or a different, but similar scenario: I'll begin trying to solve a problem. I'll search the team's documentation and find nothing, but then I'll be pointed to documentation that is exactly what I was looking for. <i>Ugh</i>.<p>So it's kind of funny, I'll be on a team with a wealth of information documenting everything, but it's borderline useless since I can't find what I need when I need it, and only Joe who has been here for 15 years knows exactly how everything is laid out and knows where to point me. How do I prevent this? How can I structure my documentation so it's easy to navigate and easy to stumble upon what you need. I can't be the only one that's had this issue, right?<p>I guess at a higher level I'm realizing that this question really is, "What's the best way to structure documentation"?<p>Additionally, any tips on how to do this in Confluence? I feel like at least 20% of the problem is due to how awful it is to create anything remotely navigable in that tool.