Slite

Why we picked it This is the 'why does nobody read our handbook' guide, and it names the real failure mode: fewer than 1 in 20 docs get updated monthly, so teams quietly drift back to Slack and the doc dies. Its fixes map directly onto your answer: assign a named owner per section, embed an 'answer with a link' habit so the doc becomes the reflex, keep it inside the tools the team already lives in (Slack, Linear, GitHub) instead of a new platform, and use staleness signals to cut dead sections, which is your 90-day rule made concrete.

Internal Documentation: How to Build Docs Your Team Actually Reads

From Slite by Slite 15 min read

• Every section needs a named owner, or it rots: undeniable ownership beats better writing
• Keep docs where work already happens and answer questions with a link, so maintaining the doc is part of daily work, not a side project
• Surface and cut stale content on a cadence, since an untouched section is almost always wrong or dead