breadcrumbs

Show page hierarchy

Install

docsloth component add @docsloth/breadcrumbs@1.0.0

Live package: sha256:eb968b49affbedc914698148b90ef848c5836bf91c6bcba8f3d5b0af5269fca6 with 2 file digest(s); the catalog entry is generated from the built package, not a placeholder.

Props

The prop schema is normative in packages/contracts/component-props/breadcrumbs.schema.json.

Example props generated from this schema:

{
  "title": "example-title",
  "items": [
    {
      "label": "example-label",
      "href": "example-href"
    }
  ]
}

Required props: items.

Example

Example document IR (the block the renderer consumes):

{
  "type": "breadcrumbs",
  "props": {
    "title": "example-title",
    "items": [
      {
        "label": "example-label",
        "href": "example-href"
      }
    ]
  }
}

Renderer HTML (entities decoded and wrapped for display):

<nav class="ds-block ds-breadcrumbs" data-component="breadcrumbs" aria-labelledby="b-title">
<h3 class="ds-block-title" id="b-title">example-title</h3>
<ol class="ds-trail">
<li>
<a href="example-href" aria-current="page">example-label</a>
</li>
</ol>
</nav>

Preview (interface-only; the markup above is the same output):

The renderer resolves this component as a native block; the preview above is its real HTML output, and Markdown parity for native blocks is covered by the renderer test suite.

Specification

Generated from packages/contracts/component-specs/breadcrumbs.md.

Contract

Production props are normative in ../contracts/component-props/breadcrumbs.schema.json. The corresponding component-fixtures manifest is only a minimal protocol fixture; use the production props schema when building the published package. The packaged artifact ships exactly its generated component-package.json manifest plus props.schema.json (the production props schema, copied byte-for-byte) and spec.md (this spec, copied byte-for-byte); it contains no executable payload, fallback implementation, Storybook, test suite, SSR harness or README. Rendering behavior and the acceptance cases below belong to the renderer and the repository tests, not to the package. Installation pins the package version and the digest of every shipped byte.

Intended behavior

Actual hierarchy with last item current, no duplicate invisible SEO links.

React rendering

The React component renders production items as a labelled navigation landmark with an ordered list of links. Only the final visible item is marked aria-current="page". HTTP(S) and relative web destinations are accepted; executable schemes and credential-bearing URLs remain readable labels without links. Empty trails and repeated normalized destinations show an unavailable state. The navigation compiler remains responsible for graph-wide cycle checks.

A trail with at least two items and valid ancestor destinations emits one Schema.org BreadcrumbList using exactly the visible labels, order and validated URLs. Missing ancestor destinations omit structured data; an unlinked final item represents the current page. Relative links and JSON-LD identifiers resolve against the hosting document. JSON serialization escapes HTML delimiters so labels cannot close the data script. Navigation works in server-rendered output without JavaScript.

Failure and fallback

Cycles rejected by navigation compiler.

Required acceptance cases

Breadcrumb JSON-LD equals visible hierarchy. Also test empty data, loading, denied access, browser without JS, mobile 360px, keyboard navigation, dark mode and an explicit constrained agent tool call. The server independently authorizes capability requests; a package manifest cannot grant authority.

Data and maintenance

Data bindings resolve from a specific publication/release vector and permitted fact/evidence graph. Configuration edits create versioned component patches. Update invalidation uses dependency IDs, never indiscriminate whole-page regeneration. Human-owned props survive automatic updates unless invalidated with an explicit conflict. Missing optional resources leave an honest inert/readable fallback, not a broken page or fake success.

Cost and tools

Pure/local interaction must never invoke a model by accident. Any model, remote query or executor call must reserve approved budget before dispatch. Public visitors do not inherit owner resources. The component may call only named tools in its signed manifest with valid typed inputs. A cancelled job stops polling and closes resources. No component gets platform administration, raw credentials or an unlimited execution loop.

Package manifest

Protocol fixture: packages/contracts/component-fixtures/breadcrumbs.json.

Sources