On this page
Rendering and Themes
Themes provide the shared shell: document structure, navigation, breadcrumbs, messages, and footer. Route pageparts own the content specific to a feature.
Rendering Boundary
Prepare data before rendering. Escape untrusted text at output, allow reviewed rich content only through an explicit sanitizer, and keep state-changing operations out of templates.
Use shared design tokens and established components for typography, spacing, buttons, cards, tables, messages, and responsive behavior. Route-specific CSS should solve a feature need without redefining the global shell.
Accessible Output
- Provide one clear page heading and a logical heading hierarchy.
- Associate labels, descriptions, and errors with form controls.
- Preserve visible keyboard focus and meaningful link text.
- Use native elements before adding custom interaction roles.
- Give diagrams an accessible name and keep essential meaning in adjacent text.