Routing, Layouts, and Modules

Recommended approach

Keep route, layout, and module structure aligned so teams can navigate and extend features without guesswork.

• Colocate route modules with feature modules.
• Use predictable naming for page, layout, and middleware files.
• Keep auth guards and redirects at routing boundaries.
• Keep shared UI and shared helpers outside feature-owned modules.

Suggested structure

Use a feature-first tree where each module owns its route entry points and feature-specific UI.

Implementation checklist

• Document route group and module naming conventions.
• Define nested layout strategy and ownership boundaries.
• Keep API communication in api/ modules, not in presentational components.
• Keep business logic out of shared UI primitives.
• Add route-level loading and error boundaries.

Common pitfalls

• Route names that encode implementation details instead of domain meaning.
• Reusing layouts that hide permission assumptions.
• Hiding feature logic in global components/ or lib/ too early.
• Mixing route files and feature files with no consistent convention.

Related pages

• State Management
• Auth on Frontend
• Data Loading and Cache