Skip to main content

Products

Use this page when you already know which tool you need, or when you need to switch from cross-stack guidance into a specific versioned product family.

When to use this page​

  • You need exact product-level docs rather than stack-level guidance.
  • You are comparing product families or narrowing an issue to one tool.
  • You need the right versioned entry point for overview, operations, security, or reference content.

Prerequisites​

  • You know the tool name or at least the product role you are looking for.
  • You understand that cross-stack concepts and runbooks may still be the better starting point if the problem is not yet narrowed.

Product model​

Product pages are versioned and owner-clear. They should be the place to go when:

  • exact tool behavior matters
  • tool-specific operations or security posture matter
  • exact product API or compatibility detail is needed

Architecture / Flow​

How to use this page​

1. Start with the product overview​

Open the stable overview first unless you specifically need another public channel.

2. Move to the exact page family​

Common next choices:

  • overview
  • operations
  • security
  • api-reference
  • compatibility

3. Escalate back to stack pages when the question crosses product boundaries​

If the issue turns out to be cross-product, switch back to:

Current tracked products​

Verification​

This page is being used correctly when:

  1. the reader can narrow to one product quickly
  2. the next click lands on a versioned product family page
  3. cross-product problems are handed back to stack-level pages instead of being forced into one product lane

Common failure modes​

Treating the products area like the best first stop for every question​

Problem:

  • readers lose the benefit of journey, concept, and operations-oriented guidance.

Better path:

  • use product pages once the issue is truly narrowed to one tool

Staying inside one product when the problem is clearly cross-stack​

Problem:

  • cross-boundary failures are misread as local product defects.

Better path:

  • hand back to stack-level concept, integration, or operations pages when the boundary widens

Next paths​