Ever feel like your documentation is playing catch-up with your product updates? Stale is your workflow for flagging outdated articles, even when you don't have everything ready to fix them yet.
Think of it as an advanced Post-it note for your Knowledge Base. You spot something out of date, stick a note on it, and move on. Your future self (or your team) can sort it out later (hopefully!).
When and Who Should Use Stale
Team | When to Mark as Stale |
Support | Customer reports outdated information |
Engineering | Features mentioned in articles get updated or removed |
Content Teams | Scheduling content reviews in upcoming sprints |
Anyone | Spotting outdated info without having update details ready |
Spotting Stale Content
A Stale badge will appear on the article row. If your article has a Stale reason, hover over the badge to read your note.
- When your article is currently Stale, a Stale notification
will appear alongside your article status dropdown. - If the article is due to go Stale in a set amount of time, the Set Stale button
will display the time left until it does.
- Inside Home, click the x stale articles pill
- This will filter and show you any articles marked as Stale
Weekly Email Reports
Automated email reports help you keep content fresh without constantly checking by hand. Each weekly report shows:
- Total count of Stale articles
- New and existing Stale articles, alongside how long they've been Stale for
To enable weekly reports:
- Head to Profile (or click here)
- Toggle on Send me weekly Stale emails
- Hit Save Changes
Next Steps
Once you've updated the content, you'll want to mark your articles as Fresh to peel off the Post-it.
Ready to leave your first note? Learn how to mark articles as Stale π