Postal Portal
A shipping product on two stacks

Jul 2025 · 2 repos · two stacks · restyles into 2026

spec-first PRD, then tech spec, then tasks. The transactional flow's commit log counts up from task 1.2 to 9.3.

A postal shipping product built across two weeks of July 2025, spec-first on both halves. The marketing site went on Adobe Edge Delivery Services as 17+ reusable authoring blocks. The transactional flow, quote through pickup through confirmation, went on Next.js: 89 commits in a six-day sprint, each one numbered against the task list it was working through.

The git history under-counts this one. The marketing repo's whole build week landed as a single commit touching 2,700+ lines, the PRD and tech spec its README points to never got committed, and the page content lives in da.live rather than git. Small restyles kept trailing in afterward; the last one landed in May 2026, ten months after the sprint.

label
Open the postal portal build diagram full size

Postal Portal build diagram: a written spec layer (PRD, tech spec, numbered task list) drives two stacks side by side. Left, the EDS marketing site with 17+ authoring blocks and content in da.live. Right, the Next.js transactional flow built as a six-day task-numbered sprint from quote to pickup to confirmation.

One spec method, two stacks. Drawn for this page from the two repos' commit history.

Jul 12 - 19, 2025 · 17+ blocks · restyles to May 2026

da-live-postal-2025-07

The marketing site on EDS and da.live: hero, cards, stats, and forms as reusable authoring blocks. The specs that drove it stayed local; the build week landed as one big commit.

Jul 19 - 25, 2025 · 89 commits in 6 days

nextjs-postal-2025-07

The transactional flow in Next.js: a task-numbered sprint, 1.2 through 9.3, from init to a Playwright-tested pickup and confirmation flow, with release branches along the way.

All projects