Skip to main content

Modules

Use this page when you already know the module or domain area you need and want the shortest path to a curated longform module explanation before dropping into versioned product detail.

When to use this page​

  • You know the tool or module name already.
  • You need a public-safe explanation of a module’s role and entry points.
  • You want to start from the manufacturer-docs longform view rather than a raw product tree.

Prerequisites​

  • You can distinguish module-level orientation from exact versioned product reference.
  • You know whether your next question is still cross-stack or already narrowed to one tool.

Module model​

The modules area is intentionally different from the products area:

  • modules:
    • curated longform entry pages grouped around role and domain understanding
  • products:
    • versioned product families for exact overview, operations, security, and reference

Architecture / Flow​

Core platform modules​

Additional tools currently available through versioned product families​

These tools are already part of the public product catalog, but do not currently materialize as standalone curated module longform pages in this reviewed bundle:

When to switch to product pages​

Switch to /products when you need:

  • exact versioned operations
  • exact security posture for one tool
  • product API reference
  • compatibility or release notes for one tool

Full product catalog​

Verification​

This page is being used correctly when:

  1. a reader can start from a known tool without repo archaeology
  2. the next click lands on a curated module page or a versioned product family intentionally
  3. readers do not confuse module orientation with exact versioned product truth

Common failure modes​

Using product pages when the question is still domain-level​

Problem:

  • the reader gets exact detail before they have the model.

Better path:

  • start with the module longform page first

Treating modules and products as duplicates​

Problem:

  • the navigation feels redundant instead of purposeful.

Better path:

  • use modules for role and domain understanding, products for exact versioned detail

Source Truth​

Next paths​