Keeping this guide up to date
When a user-visible part of Skilladder changes, the wiki should change too. This page is a reminder for whoever is shipping the change.
When to update the wiki
| Change type | What to update |
|---|---|
| A menu appears, moves, or disappears | Navigation map and any affected how-to guides |
| A role's access changes | Capabilities matrix and the relevant role page |
| A new workflow is added | Add a new how-to guide (or update an existing one) |
| Steps in an existing flow change | Update the affected how-to guide |
| Labels or button names change in the product | Update any how-to guides that reference the old label |
A quick Slack message is fine for minor tweaks. For anything that changes a step-by-step flow or a role's access, update the wiki directly so CS and ops have an accurate reference.
How-to guide format
All how-to guides follow the same structure: Goal → Who can do this → Before you start → Steps → What happens next. Match that format when adding new guides.
Letting CS know
If a change is externally visible — something customers actually use, not an internal tool — tag CS leadership in Slack after updating the wiki so they can brief their teams before customers notice.