Use this section as an orientation map for the EduSync codebase. It explains the frontend/backend boundaries, shows how a screen request reaches persistence, and provides source-linked examples. The directory trees describe the purpose of each tracked directory; dependency, build-output, cache, runtime, log, and secret-bearing folders are intentionally excluded.
Route components under src/pages compose shared and feature-specific UI from src/components. Route definitions and role access metadata live under src/navigation. Hooks, contexts, and src/lib hold reusable behavior, API access, generated Orval hooks, and model types. Generated clients should be regenerated from the API contract rather than edited by hand.
API defines HTTP routes and response metadata. APPLICATION owns request/response DTOs and service contracts; DOMAIN contains business entities and static definitions. INFRASTRUCTURE implements those contracts with EF Core, migrations, integrations, reports, caching, and seed data. TOOLS holds supporting utilities.
src/lib/orval call the typed endpoint and expose query or mutation state.These are selected excerpts from working source files, not standalone samples. Read the file link for surrounding validation, mapping, error handling, and UI details. The frontend example shows a generated query hook feeding a shared list; backend examples move from HTTP action to service contract and implementation.
Browse from the project root into the feature or platform area you need.
How to read the tree: indentation shows parent-child folders. Each entry includes its documented purpose; a structural-parent note marks an intermediate folder needed to make the hierarchy readable. Use the README links above for setup and project-level conventions.