SOP-MKT-website-update-v1.0¶
1. Purpose¶
Define how the eco|monetize™ marketing website is updated — from copy edits through structural changes — ensuring no external-facing content goes live without proper content approval and QA signoff.
Scope: This SOP governs the marketing website (ecomonetize.com or equivalent public site). It does not govern the MkDocs documentation site (eco-monetize.github.io/claude/), which is governed by SOP-DEV-mkdocs-publication-v1.0.
2. Update Classification¶
| Tier | Description | Examples |
|---|---|---|
| Tier 1 — Copy clarification | Minor language improvement; meaning unchanged; no offer or pricing language | Fixing a typo, shortening a sentence, improving readability |
| Tier 2 — Content update | New content, updated messaging, blog post, case study; no offer/pricing change | New LinkedIn-to-website landing section, new FAQ entry |
| Tier 3 — Offer/positioning change | Any update touching offer name, price, ICP language, category claims | Assessment™ price change, new offer section, category repositioning |
| Tier 4 — Structural change | New pages, navigation changes, site architecture changes | New product page, footer restructure, new subdomain |
3. Approval Requirements by Tier¶
| Tier | Content approval | Technical approval | QA |
|---|---|---|---|
| Tier 1 | category.positioning autonomous | code.platform autonomous | Spot-check by code.platform |
| Tier 2 | CMO reviews and approves | CDO aware | qa.visuals signoff required |
| Tier 3 | CMO + CEO approve (per SOP-MKT-offer-creation-v1.0 if offer-driven) | CDO approves | qa.visuals signoff + CRO cross-check on offer language |
| Tier 4 | CMO + CEO approve | CDO approves | qa.visuals full regression |
No Tier 3 or Tier 4 update ships without CEO sign-off. code.platform does not deploy without confirmed approval in Monday.com.
4. Update Procedure¶
Step 1 — Intake¶
Request arrives via: - CEO or CMO session-dir drop (Tier 2-4) - category.positioning initiative (Tier 1-2) - CRO request for offer page update (Tier 3)
All requests create a Monday.com item with: - Tier classification - Content draft or link - Required approvals - Deadline (if any)
Step 2 — Content draft¶
category.positioning authors or reviews all copy before any code work begins. No designer or developer touches website content without a reviewed content draft.
For Tier 3: council review per SOP-MKT-offer-creation-v1.0 must be complete before content draft is approved.
Step 3 — Technical implementation¶
code.platform implements per SOP-DEV-implementation-workflow-v1.0:
- Feature branch from main
- No direct-to-production pushes
- PR opened before deployment
Step 4 — QA¶
qa.visuals reviews visual output per tier requirements. For Tier 3-4, qa.visuals runs a full visual QA Report before approving the PR.
Step 5 — Deploy¶
code.platform deploys after: - All content approvals confirmed and logged in Monday.com - QA signoff in the PR - CDO (Tier 2-4) has reviewed the PR
Post-deploy: code.platform confirms live URL and runs a smoke test. Notifies CMO and CRO via #agent-handoffs that the update is live.
5. Rollback¶
If a deployed update causes regressions or requires emergency retraction:
1. git revert {commit} — no force pushes
2. code.platform notifies CDO and CMO immediately
3. SEV2 Incident Report filed per SOP-EXEC-escalation-incident-handling-v1.0
4. Root cause documented before re-deployment
6. Calendar Freeze¶
During a freeze declared per SOP-MKT-calendar-freeze-coordination-v0: - Tier 3-4 updates paused (offer and positioning language frozen) - Tier 1-2 updates may continue if they do not reference frozen content - All queued Tier 3-4 updates held in Monday.com for post-freeze release
Change Log¶
| Version | Date | Change |
|---|---|---|
| v1.0 | 2026-04-21 | Initial draft — sop.manager. |
Owner: code.platform Executive sponsor: cdo Co-sponsor: cmo (content approval authority) Drafted by: sop.manager Status: Draft — pending CDO + CMO review + approval Version: v1.0