Website project retrospective: channel & URL planning (two hundred+ staff)

Context: Last week we reviewed channel & URL planning 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 Flutter, then followed our reproduction steps. Add a field dictionary to the docs so new joiners ask fewer repeat questions.

Risks & Mitigations

Last week we reviewed search indexing diagnostics with the client's IT lead. They care more about stability than buzzwords. Editors know the CMS well enough, but search indexing diagnostics 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. This write-up is for colleagues progressing website and CMS work. The client is in beauty & wellness, roughly two hundred+ staff, based around high-tech zones. Editors know the CMS well enough, but company website development still needs a one-page rule sheet to cut verbal rework. Archive screenshots and config change IDs for this company website development round so next month's retrospective stays concrete. Last week we reviewed brand site launch with the client's IT lead. They care more about stability than buzzwords. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to brand site launch first. Archive screenshots and config change IDs for this brand site launch round so next month's retrospective stays concrete.

Delivery Approach

This write-up is for colleagues progressing website and CMS work. The client is in beauty & wellness, roughly two hundred+ staff, based around new urban centers. We hit a case of a teammate accidentally deleting a channel. Troubleshooting started with logs on Git, then followed our reproduction steps. Prefer a go-live window outside peak traffic, and prepare the rollback package early. Last week we reviewed image weight control with the client's IT lead. They care more about stability than buzzwords. Editors know the CMS well enough, but image weight control still needs a one-page rule sheet to cut verbal rework. Add a field dictionary to the docs so new joiners ask fewer repeat questions. Last week we reviewed image weight control with the client's IT lead. They care more about stability than buzzwords. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to image weight control first. Archive screenshots and config change IDs for this image weight control round so next month's retrospective stays concrete.

Background & Goals

This write-up is for colleagues progressing website and CMS work. The client is in chemical materials, roughly a hundred-person team, based around inland growth markets. We hit a case of metrics not matching finance numbers. Troubleshooting started with logs on Redis, then followed our reproduction steps. Prefer a go-live window outside peak traffic, and prepare the rollback package early. Last week we reviewed CMS publishing workflow with the client's IT lead. They care more about stability than buzzwords. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to CMS publishing workflow first. Add a field dictionary to the docs so new joiners ask fewer repeat questions.

Takeaways: This write-up is for colleagues progressing website and CMS work. The client is in home & building materials, roughly two hundred+ staff, based around new urban centers. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to CMS publishing workflow first. Archive screenshots and config change IDs for this CMS publishing workflow round so next month's retrospective stays concrete.