4 checkpoints when handling brand site launch

Context: Last week we reviewed search indexing diagnostics with the client's IT lead. They care more about stability than buzzwords. We hit a case of legacy outbound links broken. Troubleshooting started with logs on WeChat DevTools, then followed our reproduction steps. Next, we recommend to temporarily disable noncritical plugins and retest. If more features are added, scope the blast radius before scheduling.

Risks & Mitigations

Last week we reviewed CMS publishing workflow with the client's IT lead. They care more about stability than buzzwords. Editors know the CMS well enough, but CMS publishing workflow still needs a one-page rule sheet to cut verbal rework. Prefer a go-live window outside peak traffic, and prepare the rollback package early. Last week we reviewed mobile responsiveness with the client's IT lead. They care more about stability than buzzwords. QA walked the main path three times on real devices and flagged edge cases around mobile responsiveness. Next, we recommend to store backups in a separate folder with dated labels. If more features are added, scope the blast radius before scheduling. The same requirement can sound different across departments; writing it down helps align decisions on channel & URL planning. Editors know the CMS well enough, but channel & URL planning still needs a one-page rule sheet to cut verbal rework. Archive screenshots and config change IDs for this channel & URL planning round so next month's retrospective stays concrete.

Operations & Collaboration

Last week we reviewed mobile responsiveness with the client's IT lead. They care more about stability than buzzwords. QA walked the main path three times on real devices and flagged edge cases around mobile responsiveness. Prefer a go-live window outside peak traffic, and prepare the rollback package early. This write-up is for colleagues progressing website and CMS work. The client is in construction, roughly about thirty people, based around free-trade zones. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to HTTPS and certificate renewal first. Next, we recommend to require a change request for any scope change. If more features are added, scope the blast radius before scheduling.

Background & Goals

This write-up is for colleagues progressing website and CMS work. The client is in textile & apparel, roughly a dozen staff, based around inland growth markets. QA walked the main path three times on real devices and flagged edge cases around search indexing diagnostics. Next, we recommend to store backups in a separate folder with dated labels. If more features are added, scope the blast radius before scheduling. The same requirement can sound different across departments; writing it down helps align decisions on static asset caching. QA walked the main path three times on real devices and flagged edge cases around static asset caching. Prefer a go-live window outside peak traffic, and prepare the rollback package early.

Takeaways: Last week we reviewed search indexing diagnostics with the client's IT lead. They care more about stability than buzzwords. We hit a case of legacy outbound links broken. Troubleshooting started with logs on Git, then followed our reproduction steps. Add a field dictionary to the docs so new joiners ask fewer repeat questions.