Marketing Release Workflow

Cadence & Governance

• MVP — Ship baseline product, solutions, and contact content.
• Biweekly Iterations — Reserve every second Tuesday for copy, component, or analytics updates.
• Quarterly Campaigns — Align major launches with product milestones and document decisions in ADRs when scope changes.

Pre-Release Checklist

1. Sync with marketing stakeholders on messaging updates.
2. Update MDX content or components within apps/site.
3. Document Major Changes: Create or update the overhaul-walkthrough.mdx (or a versioned equivalent) for major aesthetic or architectural shifts.
4. Run pnpm install (if dependencies changed) and pnpm build:site inside Docker.
5. Capture Lighthouse metrics on the Cloudflare preview URL (desktop + mobile ≥ 90).
6. Confirm security headers in preview using curl or Mozilla Observatory.
7. Validate accessibility with keyboard navigation and axe scan.
8. Obtain approvals from marketing and security leads.

Tagging & Change Log

• Tag monorepo releases as marketing-vX.Y.Z when promoting to production.
• Record highlights in this document with the tag, date, and primary deltas.
• Reference any ADR updates or new ADRs triggered by the release.

Rollback Procedure

1. Open the Cloudflare Pages project for apps/site.
2. Promote the last known good build to production (Pages retains history).
3. Log an incident referencing the Git tag, Pages build ID, and remediation tasks.
4. Update this page to capture context for future retrospectives.

Post-Release Validation

• Monitor analytics (once approved) and contact form submissions for anomalies.
• Verify DNS + TLS status after any domain changes.
• Ensure marketing roadmap and backlog reflect newly completed work.