Codebase Cleanup & Production Hardening

Canadian Elite Volleyball Academy — Development Update • April 19, 2026

--- title: Codebase Cleanup & Production Hardening ---

Codebase Cleanup & Production Hardening

What & Why

The codebase has grown significantly — the monolithic is 37,609 lines with 709 route handlers, is 6,976 lines, and several frontend pages are extremely large (community-profile at 9,420 lines, coach-portal at 4,224, events-management at 3,999). This makes the app slower to build, harder to maintain, and more fragile in production. The goal is to split large files into well-organized modules, remove dead/unused code, and verify everything works correctly on the production app.

Done looks like

• is split into domain-specific route files under , with the monolith reduced to a thin orchestrator that imports and registers each module. No route logic remains in the monolith.
• Large frontend pages (community-profile, coach-portal, events-management, command-center) have their internal sections extracted into sub-components in dedicated directories.
• has its major method groups extracted into focused files under .
• Dead or unreachable code (unused exports, commented-out blocks, orphan routes) is removed.
• All existing functionality continues to work — no behavioral changes.
• The production app deploys and serves correctly after cleanup.

Out of scope

• No new features or UI changes.
• No schema changes to (it stays as-is at 5,484 lines since it's declarative and splitting it risks circular import issues with Drizzle).
• No changes to business logic, API behavior, or data model.
• No dependency upgrades or framework migrations.

Relevant files

Canadian Elite Volleyball Academy
elitevolleyball.training