The Templates section of the rail now opens on the decorated templates of the page's kind, covers two to a row and spreads at full width, each card the page renderer drawing the page the click will lay: this page's photos and words in it, in the book theme, a cover in the journey's title and subtitle as the assistant's layout sets it. A row of style chips narrows the set to one archetype. A click is one undo step on the page as it is then, refused for the other kind of page, and opens the photos when frames are left empty. The book's own layouts and the built-in wireframes follow below, and the help guide and the wiki describe the panel as it now is. The panel moved out of StudioSidebar into its own file; the sidebar keeps the rail, and its two physical sides went with the code, so the rtl baseline entry goes too. The Travel panel and a template's map build the journey they draw with one helper.
@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.