Healthcare firm notes on corporate website redesign

Context: This write-up is for colleagues progressing website and CMS work. The client is in maternity & baby products, roughly a hundred-person team, based around East Asia. Editors know the CMS well enough, but multilingual website build 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.

Operations & Collaboration

This write-up is for colleagues progressing website and CMS work. The client is in finance & tax consulting, roughly two hundred+ staff, based around capital business districts. Editors know the CMS well enough, but image weight control 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. The same requirement can sound different across departments; writing it down helps align decisions on multilingual website build. We hit a case of metrics not matching finance numbers. Troubleshooting started with logs on Git, then followed our reproduction steps. Next, we recommend to log API status codes and latency. If more features are added, scope the blast radius before scheduling. 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. Next, we recommend to lazy-load homepage assets by route. If more features are added, scope the blast radius before scheduling.

Background & Goals

The same requirement can sound different across departments; writing it down helps align decisions on CMS publishing workflow. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to CMS publishing workflow first. Next, we recommend to require a change request for any scope change. If more features are added, scope the blast radius before scheduling. This write-up is for colleagues progressing website and CMS work. The client is in beauty & wellness, roughly a hundred-person team, based around coastal tech hubs. We hit a case of a teammate accidentally deleting a channel. Troubleshooting started with logs on Nginx, then followed our reproduction steps. Archive screenshots and config change IDs for this corporate website redesign round so next month's retrospective stays concrete.

Risks & Mitigations

This write-up is for colleagues progressing website and CMS work. The client is in beauty & wellness, roughly about thirty people, based around Europe. We hit a case of captchas frequently failing to load. Troubleshooting started with logs on React Native, then followed our reproduction steps. Next, we recommend to require a change request for any scope change. 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 multilingual website build. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to multilingual website build 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 sports venues, roughly around fifty employees, based around economic development zones. QA walked the main path three times on real devices and flagged edge cases around multilingual website build. Prefer a go-live window outside peak traffic, and prepare the rollback package early.