Skip to content
CaddieSight Docs

Codebase map

Monorepo layout

Section titled “Monorepo layout”
CaddieSight/
├── api/            Backend API, contracts, infrastructure, APIM templates
├── clubhouse/      Golfer-facing React PWA
├── ios/            Native SwiftUI client and watch experience
├── android/        Native Jetpack Compose client
├── proshop/        Staff-facing web console
├── corp/           Marketing site built with Astro
└── docs/           Engineering documentation site built with Astro Starlight

Backend hotspots

Section titled “Backend hotspots”
  • api/CaddieSight.Api/Controllers for HTTP endpoints.
  • api/CaddieSight.Api/Application/Services for business logic.
  • api/CaddieSight.Api/Application/DTOs for API contracts.
  • api/CaddieSight.Api/Domain for entities and interfaces.
  • api/CaddieSight.Api/Infrastructure for EF Core, storage, auth, and external integrations.

Frontend hotspots

Section titled “Frontend hotspots”
  • clubhouse/src/pages for top-level pages.
  • clubhouse/src/api for backend access.
  • clubhouse/src/context for shared state such as profile hydration.
  • clubhouse/src/types for shared contracts.

Native hotspots

Section titled “Native hotspots”
  • ios/CaddieSight/Features for screens and flows.
  • ios/CaddieSight/Networking for HTTP access.
  • android/app/src/main/java/com/caddiesight/feature for screens.
  • android/app/src/main/java/com/caddiesight/network for HTTP access.

Operational hotspots

Section titled “Operational hotspots”
  • .github/workflows for CI/CD.
  • docker-compose.yml for local infrastructure support.
  • api/apim for API Management policies and templates.

Practical navigation tips

Section titled “Practical navigation tips”
  • Start from controllers when you know the route.
  • Start from Application/Services when you know the business capability.
  • Start from types, Models.swift, or Models.kt when tracing contract changes.
  • Check the matching workflow before changing how a surface builds or deploys.