Skip to content

docs: adopt Fumadocs components for clarity (highlights, Tabs, Steps, TypeTable, Accordion)#186

Merged
austenstone merged 2 commits into
mainfrom
austenstone-fumadocs-components-audit
Jun 22, 2026
Merged

docs: adopt Fumadocs components for clarity (highlights, Tabs, Steps, TypeTable, Accordion)#186
austenstone merged 2 commits into
mainfrom
austenstone-fumadocs-components-audit

Conversation

@austenstone

Copy link
Copy Markdown
Owner

What

Five green-lit Fumadocs UI adoptions to sharpen the docs message. Implements the audit proposal (fumadocs-component-audit.md).

Changes

  1. ① Code highlighting[!code highlight] markers on the synthesized lines inside CodeCompare "generated .yml" panes across 11 macro pages (retry, fallback, soft-fail, dynamic-matrix, if-changed, share, ref, injection-hoist, lifecycle, expand-matrix). Makes it visually obvious what each macro injects vs. what you wrote. Headline win.
  2. ② Tabs — real ts/js/json examples in configuration.mdx #config-formats (registered Tabs/Tab, not the codeblock tab= variant).
  3. ③ Stepsquickstart.mdx init→build→check, and supply-chain.mdx's two-phase pattern.
  4. ④ TypeTable — macro option lists for retry + fallback (soft-fail already had one).
  5. ⑤ Accordionout-of-scope.mdx collapses the issue lists under each numbered cause; H2 headers + "Why not" kept visible.

Registration (docs/components/mdx.tsx)

Purely additive: Accordion/Accordions + Step/Steps imports and return-object entries. No removals; existing entries untouched.

Gates

  • npm run docs:build — green (503/503 static pages)
  • npm test -- docs-completeness syntax-reference macros84/84 passing
  • ✅ Rendered-HTML check on edited pages: highlights render (highlighted class), zero literal [!code highlight leaks (markers strip cleanly even across run: |- block scalars).

Merge reconciliation (three-way hotspot)

docs/components/mdx.tsx is touched by two other in-flight workstreams. My append is additive and should merge cleanly with:

  • The Files work (File/Files/Folder registration + <Files> trees in quickstart/configuration/templates) — left untouched here; my Steps/Tabs edits sit in different regions of those files.
  • The Twoslash work (source.config.ts + Popup components) — source.config.ts not touched by this PR.

Draft until the above land and the registry is reconciled.

Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com

austenstone and others added 2 commits June 22, 2026 14:47
… TypeTable, Accordion)

Five clarity wins across the Actio docs:
- Code highlighting ([!code highlight]) on synthesized lines in CodeCompare
  generated panes across 11 macro pages, so it's obvious what each macro adds.
- Tabs (ts/js/json) in configuration.mdx #config-formats.
- Steps in quickstart.mdx (init->build->check) and supply-chain.mdx two-phase flow.
- TypeTable for macro option lists (retry, fallback; soft-fail pre-existing).
- Accordion in out-of-scope.mdx collapsing issue lists under each cause (H2s kept).

Registration in docs/components/mdx.tsx is additive (Accordion/Accordions, Step/Steps).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…components-audit

# Conflicts:
#	docs/content/docs/configuration.mdx
@austenstone austenstone marked this pull request as ready for review June 22, 2026 19:09
@austenstone austenstone merged commit d7e48bb into main Jun 22, 2026
8 checks passed
@austenstone austenstone deleted the austenstone-fumadocs-components-audit branch June 22, 2026 19:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant