Route readers through a multi-product docs homepage
Compare use-case, capability and experience-level navigation without forcing every reader through the same onboarding sequence.
A broad platform has readers with different questions. A new user may know a business task, an engineer may know the required API, and a returning user may need reference information. A useful homepage gives each an intelligible route.
Apply the pattern
List the distinct decisions readers arrive with: their task, technology stack, deployment preference or experience level.
Choose the primary route by the decision most likely to distinguish their next guide. Add secondary routes only when they answer a different question.
Use link labels that describe the destination's outcome. Separate concept explanations, setup tutorials and reference pages.
Review navigation with real questions: where would a beginner start, and where would an experienced integrator find an API detail? Remove routes that point to the same undifferentiated page.
Where judgment matters
More navigation options create a maintenance obligation. Add them because useful underlying content exists, and avoid implying that every product needs a large framework grid or learning academy.