How content moves from Directus or the fixture into typed modules, and the shared contracts that keep the exporter and the site in agreement.

flowchart LR
  D["Directus<br/>published rows"] -- "fetchers" --> EX["export-fallbacks.ts"]
  FX["packages/shared/fixtures<br/>export-data.json"] --> EX
  C[".cms-cache.json<br/>local only"] -. "soft fallback" .-> EX
  EX -- "validate with<br/>@repo/shared schemas" --> EM["emitter registry"]
  EM --> MOD["apps/web/src/lib/content<br/>21 modules"]
  MAN["assets-manifest.json<br/>assets-id-map.json"] --> EX
  EX --> MV["media variants"]
  D -- "Build Bot read<br/>unmirrored images" --> BM["static/images/cms<br/>generated, ignored"]
  EX --> BM

Source policy

Saving CMS content does not itself start a build. A production build uses live CMS content, whether triggered by Publish site or a merge to main. A merge after a CMS content write therefore publishes that content when the production build succeeds; the code diff does not bound the content published.

The whole live fetch has a 60 second stall guard. Exit codes come from decideExit: under the production fail policy anything but a live export fails, and every policy fails when no source exists.

What the exporter enforces

• The complete 21-output registry is built and validated before anything is written.
• Live exports also validate legal truths and explicit SEO description lengths (lib/validators/live-export.ts).
• Blog posts and projects export only when published; drafts are never public.
• Required block_* singletons must be published, or the live build fails.
• An archived optional site_pages section disappears from routes, OG cards, LLM text and the sitemap on the next build. The /, /services, /projects and /blog entries are required, and the last three must have listing type: archiving one fails export, so the build fails and the active production deployment keeps serving.
• Every committed media mirror listed in fixtures/assets-manifest.json must exist and match its SHA-256 digest.
• A live export publishes every referenced raster image without a committed mirror. It reads the original from https://cms.yesid.dev with the build token, checks the decoded image (PNG, JPEG, WebP, GIF or AVIF; 20 MiB; 16,000 px per axis; 40 million pixels; one frame) and, after all content validates, writes it with responsive WebP variants to apps/web/static/images/cms/<file-uuid>/<sha256>.<ext>. A new SVG, an unreadable file or an image block with neither a CMS file nor a site-local path fails export. Fixture exports map such references to a labelled placeholder without network (lib/build-media.ts, lib/content-media.ts).
• Encodings are cached in the Git-ignored apps/web/.cache/cms-media/, keyed by source hash and re-checked before reuse; originals are read on every live export.
• Image blocks may carry layout (row or beside) and showBothThemes; the shared schema rejects other layout values (packages/shared/src/types/blocks.ts).
• Each project one_liner is normalized to NFC and must render in full on the project OG card at 18px or larger with the bundled fonts, or export fails naming the project, locale and field (web/src/lib/og/validate-project-lines.ts).

Generated modules

lib/export-modules.ts is the single registry for fetches, schemas, cross-entity checks and outputs. emitters/configs.ts derives output configurations from it. Fetchers in lib/fetchers/ map Directus rows to product types.