← Crafts
Locale preview

Locale

Civic pilot Solo full-stack engineer

Digos civic platform — one backend authoring surface for website, mobile app, admin, and OpenData APIs without duplicating city facts.

Problem

City information fragments across website copy, mobile screens, and open-data exports. Locale (betterdigos + betterdigos-api) treats the backend as the single source: hotlines, services, governance documents, and datasets are authored once and projected to four route surfaces.

Capabilities

  • Route surfaces: /api/v1/web, /api/v1/app, /api/v1/admin, /opendata/v1/* (backend-only — no frontends in API repo)
  • Better Auth at /api/auth/*; OpenAPI-driven contracts for separate client teams
  • @betterdigos/cms on Payload 3 with Postgres, Lexical rich text, and S3 storage
  • SST and Turborepo monorepo layout with oxlint/oxfmt governance
  • Cloudflare Workers deploy path on API (wrangler, Vitest pool workers)
  • ADR-driven implementation: GOAL.md, PLAN.md, CONTEXT.md, TASK.md gate changes
CMS + stewardship Civic backend /api/v1/web /api/v1/app /api/v1/admin /opendata/v1
Four API projections from one civic backend
The backend must support Website, Mobile App, Admin, and OpenData, but it must only
implement backend contracts, schemas, persistence, auth, authorization, files, tests,
documentation, and deployment support. No frontend code belongs in this implementation.
Digos civic API and CMS
Screenshot placeholder — admin publishing flow and public API composition.