Saved to the database — shared across the team. Click any task to expand and add notes or links to evidence / existing artifacts. Use Reset to clear everything.
1 — Product, content & design 6 Pages, components, and pre-launch hardening.
Finalize content across remaining pages and post types
Before launch A few pages and post-type templates still need a review pass before launch.
› Polish the design-system component library
Before launch Final pass on edge-case states and responsive behavior.
› Design review call — walk the team through the design-system page
Before launch Surface any improvements and lock the system before launch.
› Configure Cloudflare protection (rate limiting) for pre-launch
Before launch Defensive baseline against scraping and abuse on launch day.
› Evaluate and (likely) enable two-factor authentication
Before launch For admin / CMS access. Nice-to-have but recommended pre-launch.
› Build an internal “all links” page and bulk-check HTTP 200
Before launch Renders every internal link on one page so the full inventory can be crawled in a single pass.
› 2 — Infrastructure, SEO & migration 6 Routing continuity, DNS, and platform readiness.
Export redirects from the legacy WordPress DB and import into the new system
Critical Before launch Critical: must ship before launch to avoid 404s and lost Google Search rankings.
› Add the required DNS records ahead of time
Before launch Stage them early so the cutover is just a flip.
› Provision SSL certificates ahead of the cutover
Before launch › Schedule the domain switch for a weekend
Launch window DNS propagation can take up to 24 hours — use the lowest-traffic window.
› Coordinate with the platform team to lock all infra by Friday
Before launch › Move the Vercel project from personal to corporate account
Post-launch Not blocking launch — schedule for after.
› 3 — Marketing & analytics 1 Tracking, search console, and measurement plumbing.
Run a 30-min tracking sync to wire Google Analytics and review Google Search setup
Before launch Confirm tag deployment, event names, conversion definitions, and search-console verification.
› Process and visibility across the team.
Convert the kickoff meeting transcript into a concrete task list
In parallel › Update meeting minutes in the team chat so everyone shares the same plan
In parallel › 5 — Post-launch & roadmap 4 What happens after the cutover.
Run a CMS training session for the team (copywriters, designers)
Post-launch Walk through authoring inside Payload CMS — what changed vs. WordPress.
› Hold the Thursday roadmap meeting for the next phase of the marketing site
Post-launch › Discuss MCP integration for Claude (already tested locally)
Roadmap › Plan Engram personalised memory rollout with EU AI Act compliance
Roadmap › 