new_siteadmin_api

Scaffolding a Site Admin API endpoint requires updating the OpenAPI spec, regenerating models, writing handlers, wiring dependencies, and verifying builds. This process ensures spec, models, and Go handlers are created together to avoid omissions.

Adding a route to the siteadmin server requires updating `docs/api/siteadmin-api.yaml` with error responses and schemas, running `make generate`, creating the Go handler, registering dependencies via wire injectors, and verifying the go build.

Updating OpenAPI specs for Go APIs involves documenting schemas and error responses in `docs/api/siteadmin-api.yaml` before running `make generate`. This syncs the generated models with the spec to maintain consistency across the siteadmin server.

Scaffolding siteadmin API handlers includes dependency injection wiring. The process covers dependency registration, router configuration, and wire injectors to ensure new routes integrate cleanly with the existing siteadmin server architecture.

The best way to structure Go handlers for new API routes is using the required handler structure with parameter parsing helpers and validation expectations. This covers GET, POST, and DELETE routes while satisfying project conventions for error handling.

A siteadmin API build may fail after adding a new route if dependency wiring, router registration, or go build verification steps are incomplete. Ensuring all spec updates, generated models, and handler dependencies are created together prevents build failures.