Guidance Setup is about creating the spaces where your system is explained and supported. This could be a central hub for long-form documentation, or additional places for specific audiences, platforms, or temporary needs. Good setup balances clarity with flexibility, making sure people can find what they need when they need it. Use this to decide where guidance belongs, whether that is a single site, multiple spaces, or a mix of short-lived and permanent resources.
How to
-
Define purpose
Start with the who, what, and when. Who is your guidance for, such as designers, engineers, or content teams? What decisions should it support? When will people need it most in their workflow?
-
Audit current tools
Review existing spaces such as wikis, repos, or internal sites. Note where they already serve your needs and where they fall short.
-
Research documentation approaches
Look at the range of options available, from centralised hubs to role or platform specific spaces to lightweight short-term docs. Focus on what fits your audience and scales with your system.
-
Set standards
Define what each page or space must include, such as anatomy, behaviour, accessibility, and content guidance, so it stays consistent across locations.
-
Record decisions
Capture important decisions alongside specs so context is not lost. You may also include an optional changelog section, linking back to Versioning and System Updates for a full history of changes.
-
Start small and evolve
Begin with the most critical guidance in the most visible place. Add other spaces as needed for specific audiences or temporary guidance. Test with users, then expand as your system and audience grow.