technical cleaning

Maintenance

Technical cleaning plan: dependencies, env, webhooks, stale pages, broken flows, security headers, and old content.

Technical cleaning makes the site boringly reliable, a rare luxury for a mystical house.

Dependency review

Cadence: monthly

Owner: technical owner

Dependencies are reviewed without blind upgrade frenzy.

Env review

Cadence: monthly

Owner: technical owner

Required keys match docs, unused keys are removed from notes.

Stale page cleanup

Cadence: monthly

Owner: editor

Old internal pages are updated, archived, or redirected.

Technical pass

Code and infrastructure check without adding new features.

  • Run typecheck, lint, tests, links, route audit, and security check.
  • Check Stripe, Supabase, Resend, and Vercel env notes.
  • Review noindex headers for internal sections.

Content debt pass

Even internal pages age and begin whispering outdated instructions.

  • Mark stale instructions.
  • Merge duplicate internal playbooks.
  • Archive pages that no longer match the product.

alerts

  • A deploy note says one thing and the code expects another.
  • Internal pages are indexed or linked from public conversion pages.
  • A broken flow is accepted as normal because it has a workaround.

handoff

  • Maintenance output becomes either a fix, a documented known issue, or a removed task.
  • If maintenance finds customer impact, create support ops note.

related doors