> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mzizi.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Component backlinks

> The stable URL graph that ties every registry component to its documentation, source, version history and health probe.

Every component in the registry has a set of canonical URLs. The table below says which
answer today, checked against `button` on 30 September 2026. Several of the portal's old
per-component pages did not survive the move of `mzizi.dev` to the site, and the health and
chaos probes depended on console data that the registry no longer holds.

## URL structure

| Endpoint | URL pattern | Purpose | On 30 Sep 2026 |
| - | - | - | - |
| Portal | `mzizi.dev/components/{name}` | Documentation page | `200` |
| API — component | `api.mzizi.dev/v1/ui/{name}` | Component metadata and source, shadcn format | `200` |
| API — Rust | `api.mzizi.dev/v1/rs/{name}` | The Dioxus source, where one exists | `200` |
| API — docs | `api.mzizi.dev/v1/ui/{name}/docs` | Use cases, variants, accessibility notes | `200` |
| API — versions | `api.mzizi.dev/v1/ui/{name}/versions` | Per-component version JSON | `503`: console data, not the registry's |
| Source | `mzizi.dev/source/{name}` | Full source view | `404` |
| Changelog | `mzizi.dev/changelog/{name}` | Per-component version history | `404` |
| Health | `/api/health/{name}` | Per-component health probe | Not served |
| Chaos | `/api/chaos/{name}` | Supported-fault manifest | Not served |

The API's own liveness probe is `api.mzizi.dev/v1/health`. For why the two API routes answer
`503`, see [the API gateway](/platform/api-gateway#one-route-answers-503).

## Status semantics, as designed

The health and chaos probes are not served on 30 September 2026. This is what they are
specified to answer.

For `/api/health/{name}`:

* `200` — the component exists.
* `404` — no component by that name.

For `/api/chaos/{name}`:

* `GET 200` — returns the supported-fault manifest for the component: render error, slow
  render, missing data, network timeout.
* `POST 405` — by design. Chaos injection is in-process; install the N8 `chaos` library into
  your own application rather than pointing faults at a shared service.

## DOM integration

Every rendered component carries a `data-portal` attribute pointing at its portal page:

```html theme={null}
<div data-slot="mzizi-section" data-portal="https://mzizi.dev/components/mzizi-section">
```

That single attribute is what makes several things possible at once:

* DevTools inspection clicks through to the component's documentation.
* Error tracking enriches a stack trace with a documentation link.
* N8 chaos testing looks up the supported-fault manifest by stable URL.
* The N9 fundi rung resolves a rendered component back to its canonical documentation.

The attribute is emitted by the component itself, so it stays correct without anyone
maintaining a mapping table.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.