Platforms

A catalog of platform clusters and when each one should be used

Platforms does not replace the ecosystem page. It answers a more practical question: which cluster serves which need, what it contains, and where someone should go after opening it.

Platform map

Six primary clusters shaping the public and member structure of the system

Role: connect into operations

Partner and contact cluster

Open partner

When to open which route

Use platforms as an orientation map before going deep

  • Need the whole picture

    Open Ecosystem first, then come back here to choose the right cluster for the next move.

  • Need usable resources now

    Go to Library. If you need a structured order, move from Library into Academy.

  • Want live execution context

    Go to Projects. From there the next route is usually Ecosystem, Partner, or Contact.

  • Want to start collaborating

    Go to Partner for long-term context; use Contact for a short and direct intake.

Community positioning

Community is an inner layer of the system, no longer a confusing top-level route

Community still exists as a footer destination and as a layer between newsletter, academy, partner, and other forms of participation. It should not stand as a primary promise in navigation.

Start by intent

Three routes to open after using the platform map

Library

Open it when you need frameworks, guides, or reusable materials right away.

Open library

Academy

Open it when you need structured learning order and clear paths.

Open academy

Partner

Open it when the context is clear enough to move from reading into real collaboration or implementation.

Open collaboration paths