Record Facts Table
Quiet operational facts block for timestamps, paths, owners, and record metadata.
LLM handoff
Copy a concise page brief or the full MDX source without digging through the docs shell.
- Saved
- Mar 27, 2026 10:42 AM
- Folder
- feedback/docs-nav-density
- Images
- 3 artifacts
RecordFactsTable renders routine facts in a stable key/value structure. It is designed for operational metadata that should support a route without becoming a strip of metrics or a pile of ad hoc text rows.
Installation
Install
Purchase access, then open /account/install to issue a registry token.Usage
import { RecordFactsTable } from "@/registry/swiss/blocks/record-facts-table"<RecordFactsTable
rows={[
{ label: "Saved", value: "Mar 27, 2026 10:42 AM" },
{ label: "Folder", value: "feedback/docs-nav-density" },
]}
/>Why This Block Exists
Operational surfaces often over-promote routine facts into cards or metrics. This block keeps factual data quiet, aligned, and legible.
Examples
Default
- Saved
- Mar 27, 2026 10:42 AM
- Folder
- feedback/docs-nav-density
- Images
- 3 artifacts
In Context
Why it matters
Operational facts should stay in a table rhythm. This keeps timestamps, paths, and record state quiet enough to support the main artifact instead of becoming a row of metrics.
- Route
- /feedback
- Selector
- .docs-sidebar [data-slot=trigger]
- Saved
- Mar 27, 2026 9:18 AM
- Owner
- Design systems
Guidance
- Use it for timestamps, routes, paths, selectors, owners, and saved state.
- Keep values literal and specific.
- Use a stronger shell around the table only when the page needs a real zone boundary.
API Reference
RecordFactsTable
| Prop | Type | Default |
|---|---|---|
rows | Array<{ label: string; value: ReactNode; icon?: ComponentType; action?: ReactNode }> | required |
columns | 1 | 2 | 1 |
bordered | boolean | true |
density | "compact" | "default" | "default" |
className | string | undefined |