Editorial draft available to read. Factual and language review is pending. Examples are illustrative.
Separate families and tasks
Group services visitors see as related using explicit names. Need-based entries can help different audiences, but every technology term does not need a category. Top-level links should answer what you do, whom you serve, how you work or how to begin.
Avoid dead ends
Link overview pages to services, guides and contact. Show current location and a return route. Test mobile and keyboard closing of menus. Alternative paths should remain consistent so the same service does not appear to change depending on entry point.
Test task finding
Example: ask one person to find CRM integration and another production-management help. Observe first choices and backtracking without guidance. They should explain their location, findings and next step. Clarify equivalent-looking labels before adding more menu levels.
Key takeaways
- Organise entry points around visitor decisions, not the internal organisation chart.