Refresh docs after API split

This commit is contained in:
2026-01-28 17:21:23 +01:00
parent bb55cf7dde
commit 1129947183

View File

@@ -38,12 +38,15 @@ Also see the other related files: API.md, IIS.md, SPEC.md
## Repo Layout Target
- `Program.cs` — Minimal API endpoints, middleware, cookie identity, admin endpoints
- `Data/` — EF Core DbContext and migrations (optional for MVP)
- `Program.cs` — Minimal host wiring (services, middleware, endpoint maps)
- `Endpoints/` — Minimal API route files split by area (state, suggest, vote, results, admin) + helpers
- `Contracts/` — DTOs and request records
- `Data/` — EF Core DbContext and migrations
- `Domain/` — Plain models: Player, Suggestion, Vote, AppState, Phase enum
- `wwwroot/`
- `index.html` — app shell; loads phase-specific views
- `app.js`API client + render functions + polling
- `app.js`main client script (ES module)
- `js/` — shared frontend modules (e.g., API client)
- `styles.css` — minimal styling
Do not introduce MVC controllers, Razor Pages, Blazor, or SPA frameworks.
@@ -79,3 +82,4 @@ Do not introduce MVC controllers, Razor Pages, Blazor, or SPA frameworks.
- Keep changes small and testable
- Prefer clarity over abstraction
- After every iteration, do a git commit with a brief summary of the changes as a commit message.
- Keep endpoint logic in `Endpoints/` and shared helpers/DTOs in their folders to avoid Program.cs bloat.