r2-sys-integrate

To set up menu-driven routing, configure menu.yaml with your navigation hierarchy and run the integration workflow to auto-generate route registrations and dynamic navigation components. The system reads menu.yaml to wire Leptos routes and compose modules into a unified pages structure without renaming them.

Integrating multiple UI modules involves composing them into a unified pages structure via an automated workflow that wires routes from menu.yaml without renaming modules. It generates global state management, layout components, and aggregates type definitions to ensure consistent module composition.

Yes, Tailwind theming and design system tokens are applied across all modules. The integration generates global style configurations and aligns the UI based on .r2mo/spec files and design tokens to ensure visual consistency throughout the entire menu-driven frontend system.

No, the module integration workflow does not require renaming existing Leptos components. It explicitly wires modules into the unified pages structure and registers routes from menu.yaml while preserving original module names, component structures, and existing type definitions.

Global state management is configured through an automated context and provider setup generated during module integration. The workflow aggregates type definitions and establishes the root layout configuration to ensure state is accessible across all registered routes and composed modules.