ui-plugin-guidelines

Schema-form renderer compatibility categorizes UI component mappings into direct, custom, and fallback tiers. This classification standardizes how libraries like MUI or Ant Design interact with renderer contracts to ensure consistent integration.

The recommended project structure for a schema-form UI plugin defines specific directory layouts, file naming rules, and import/export patterns. This structure ensures reliable plugin implementation and maintainable renderer component architecture.

To ensure accessibility compliance in schema-form renderers, implement an accessibility checklist covering ARIA attributes and keyboard navigation. This guarantees WCAG-friendly interactions across all mapped UI components.

Chakra UI and Mantine are supported by the canard/schema-form plugin. The plugin provides compatibility matrices that define their component mapping grades and specific configuration steps for reliable renderer integration.

UI plugin implementation requires concrete frontmatter definitions and component interfaces. These specifications establish the necessary configuration steps and contracts to enable automated checks and reliable plugin functionality.

Fallback mappings for Headless UI components indicate a lack of direct compatibility with schema-form renderer contracts. This means custom implementations are required to bridge gaps and maintain full functionality and accessibility.