Sdk Language Grid

About this block

Sdk Language Grid answers the first question a developer asks silently, does it support my stack. Nine cards, one per language, each with the install command in a mono strip and an Official or Community badge that tells the truth about maintenance. The closing line links the public spec and the policy that funds community maintainers, which reads as confidence.

Each card is three fields in one array. Badges are the only color, so official versus community scans instantly.

When to use

Reach for this block on developer pages after the quickstart has shown one language end to end. It also belongs on docs hubs where SDK choice is the first fork in the path.

A natural flow around it on a Marketing Pro page:

Before

• Quickstart steps proving depth in one language before claiming breadth

After

• Integrations for the no code half of the audience
• CTA with the API key signup

What you can display

One strong use is your real SDK matrix with honest badges. Other grids:

• Framework adapters. Next, Rails, Laravel, Django cards with install lines.
• Platform agents. One card per OS or cloud with its install command.
• Data connectors. Warehouses and queues you read from.

Tip: keep the Community badge for clients you do not maintain, claiming them as official costs trust when issues go stale.