What

Locked the first release scope, replaced the starter shell, defined the paper and document types, and created the initial Marcel profile as typed repository data.

How

Followed the roadmap sequence: foundation freeze, app skeleton and tokens, then domain model and sample content before any PDF work started.

What

Built the reusable CV document component and wrapped it in the homepage workspace with version selection and browser preview.

How

Implemented the shared markup first, then added the showcase route so the document could be reviewed in the browser before print and export paths were introduced.

What

Added dedicated print routes for A4 and Letter, then tuned spacing and vertical rhythm so the shorter Letter page still looked deliberate.

How

Kept the markup shared and moved paper differences into explicit layout tokens instead of creating separate document branches.

What

Added the Playwright PDF renderer, then switched delivery to pre-generated static PDF assets so the site can deploy on Cloudflare Pages without a Node runtime.

How

Opened the internal print route in headless Chromium, waited for print readiness and loaded fonts, called `page.pdf()` with explicit A4 or Letter settings, and wrote the finished files into the static asset tree.

What

Added PDF smoke tests, production-style app startup for Playwright, final documentation updates, and manual preview-versus-export checks.

How

Used request-level end-to-end tests for the PDF contract, then closed the loop with lint, unit tests, build verification, and visual comparison of print routes against exported PDFs.

Problem

The first print/export pass depended too much on normal browser flow, so long sections could break at awkward points once the document crossed a page boundary. The result looked unpredictable instead of intentionally designed.

Fix

The first correction was to measure rendered sections on the print route and force a page break before a section when its heading plus first printable unit would overflow the remaining page space. That moved the decision from passive CSS flow to an explicit pagination plan.

Result

This stabilized the biggest errors, but it also exposed a second issue: moving whole sections could leave a large empty area at the bottom of page 1 and a heavy content block at the top of page 2.

Problem

Section-level planning was still too coarse for dense sections such as professional experience. If an entire section had to move, the previous page could end with a lot of wasted space.

Fix

The renderer was refined to mark printable subsection units with `data-cv-unit`, then the planner started paging by section heading plus units instead of treating the whole section as one rectangle. In `Professional experience`, each role is now treated as one printable unit, so roles can move cleanly between pages without splitting the whole section too early.

Result

Pagination became much more intentional. The print route now measures sections and subsection units, applies the plan to the DOM, shows continuation headings where needed, and only then marks the route ready for Playwright PDF export.