Maurice
a19fdf6161
design-templated-framing.ts builds the pages around the chapters of a book laid on the designed templates. The cover is laid on one of the theme archetype's cover templates, poured from a page whose title and subtitle are bound to the journey, so the binding survives; an archetype with no cover for the photos there are has its cover composed as before. The journey at a glance is its map with a photo at every stop beside the figures as a poster (tiles for the collage and grid books, a sign for the postcard ones), a ticket stub of how far and how long, and the furthest point on an odometer. The countries are one country's map cut to its shape beside its stamp, a card each for up to twelve, one panel of stamps past that. The back cover adds a band of days, places and photos and a row of country stamps. A page of words, where no template takes a story, sets it beside the stop's map, its day as a stamp and its country as a tag. None of these sets a summary, a country or a mark in the classic look.
@trek/shared
Single source of truth for TREK's API contracts, expressed as Zod schemas and consumed by both the server (request validation + inferred DTO types) and the client (typed requests/responses).
This package is part of the incremental NestJS + React 19 migration (see the "Brownfield Rewrite" board). It is intentionally dormant until modules start importing it — adding it changes nothing for users.
Rules
- One folder per domain:
src/<domain>/<domain>.schema.ts(+.spec.ts). - Domain-agnostic building blocks live in
src/common/. - A route is only considered migrated once its contract lives here.
- Schemas are the source of truth; server DTOs and client types are inferred from them
(
z.infer<typeof schema>), never hand-duplicated.
Consumption (dev)
Both apps resolve @trek/shared to this package's TypeScript source:
- Server (
tsx): viapathsinserver/tsconfig.json. - Client (
vite): viaresolve.aliasinclient/vite.config.ts(+pathsfor the type-checker).
Production packaging (Docker / workspace wiring) is introduced in card F2, when the server first depends on this package at runtime. Until then prod builds are untouched.
Not yet here
The canonical error envelope is finalised in card F5 (it must match TREK's current Express error responses byte-for-byte), so it is deliberately not invented in F1.