Documentation
Integrations
Use the existing form, table, and chart contracts. Keep application transport explicit.
TanStack Form
Mizen exports useForm and the Field bridge for TanStack Form. Bind a form.Field through Field's field prop. Keep validation in the form engine and show its result with FieldError.
Use the documented form.Subscribe pattern for submit state. The app's onSubmit owns persistence and server error handling. Local examples demonstrate validation and state, not a live backend.
TanStack Table
Use Table for semantic rows and cells. Use DataTable for the TanStack Table model, sorting, filtering, selection, pagination, and supported virtualization. Keep column definitions and row identity explicit.
The application owns data fetching and server-side operations. A client filter or sort is not a server query. Keep bulk actions tied to the correct selected records and clarify whether selection spans pages.
TanStack Charts
ChartFrame integrates TanStack Charts with Mizen tokens and accessible presentation. Use ChartLegend and ChartTooltip with the documented chart model. Higher-level data components cover time series, distribution, comparison, and other reviewed tasks.
Keep underlying values precise while formatting compact axis ticks. Provide labels, units, and a readable summary. Do not add a second chart theme or a different chart engine to reproduce existing behavior.
Markdown content
Mizen ships no Markdown parser. Render documents with the parser your app already trusts, such as react-markdown with remark-gfm, inside Markdown with markdownComponents. Treat external content as data: skip raw HTML and keep URL sanitizing. Keep artifact and source links within the documented URL contracts.
Mizen has no resizable panels. When an app needs a splitter, it brings its own, such as react-resizable-panels, and owns its keyboard behavior, minimum sizes, and persistence.