Skip to content

Developer

Developer docs are for people changing Wavemap code or reviewing the platform’s technical direction.

This section owns durable explanations of architecture, testing, release identity, project planning conventions, ADRs, and the docs-site content model. It should stay useful even when an implementation detail still lives in a roadmap or app-local note.

  • The Monorepo Map explains how the apps, shared packages, CLI, operations layer, infrastructure, and docs site fit together to support the overall platform.
  • Feature Slice Workflow explains how cross-app feature work should move through contracts, apps, packages, tests, and docs as it takes shape and finalizes.
  • Local Development Runtime explains local app startup, Docker-backed services, env files, i18n assets, media modes, and Playwright runtime setup.
  • Testing explains which verification layer gives the cheapest useful signal for a given change.
  • Front End Patterns records reusable component, page wrapper, query state, saved-view, workflow hook, and label-map conventions.
  • Media Workflow And Validation explains when to use mocked storage, local emulators, deployed-dev media proof, browser media smoke, and discrepancy reporting.
  • Architecture explains durable system boundaries after roadmap work settles.
  • API Contracts records shared routes, DTOs, envelopes, query controls, permissions, and domain-code contracts.
  • Authentication And Authorization records the current auth model, enforcement layers, frontend route-access patterns, and role/permission contract.
  • Configuration And Secrets records source ownership, visibility boundaries, and verification rules for configuration changes.
  • Media Storage And Delivery records the current media model boundaries, storage runtime separation, adapter rules, and ingest/delivery posture.
  • Domain Relationships records association-row modeling and relationship-management surfaces.
  • Query Controls And Browsing State records query-control contracts, data-heavy browsing pages, URL state, and saved-view boundaries.
  • Public Entity Identifiers records the public ID, slug, URL, DTO, and collision-retry convention for public entities.
  • Content Entity Governance records lifecycle, provenance, deletion, ownership/control, and audit vocabulary for primary content entities.
  • i18n explains localization architecture, translation resources, runtime loading, asset delivery, and verification guardrails.
  • Roadmaps describes how working notes feed stable docs.
  • ADRs defines when a durable decision should become a decision record.
  • Docs Content Model explains what belongs in curated docs versus working notes.

Developers are also expected to read the admin and operations sections when their changes affect those audiences.