[hombre_fatal]

The problem that comes to mind is that every question and answer that’s posted is something you have to maintain as part of your docs as they rot over time.

I’d be curious to hear what the common solutions to that are.

Maybe it can be used as a limbo to gather FAQs that get crystallized into the real docs and then deleted.

[klodolph]

I think a reasonable solution is “people who find the answer should observe that the question was asked eight years ago, and certainly double-check the answer”. If it’s a question about company internal codebases or operations, then you should have access to see the code or resources the answer is talking about.

[PunchyHamster]

Yeah, our wiki is full of old no longer actual/relevant articles and very little incentive to fix any of that vs go work on the next ticket.

I even pondered adding a bot that would create ticket out of oldest not-updated article for someone to go thru and verify it's still current/relevant