Website project retrospective: multilingual website build (about thirty people)

Context: This write-up is for colleagues progressing website and CMS work. The client is in construction, roughly two hundred+ staff, based around high-tech zones. QA walked the main path three times on real devices and flagged edge cases around role-based access control. Add a field dictionary to the docs so new joiners ask fewer repeat questions.

Background & Goals

Last week we reviewed product-site information architecture 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 product-site information architecture. 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 search indexing diagnostics. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to search indexing diagnostics first. Archive screenshots and config change IDs for this search indexing diagnostics round so next month's retrospective stays concrete.

Operations & Collaboration

The same requirement can sound different across departments; writing it down helps align decisions on role-based access control. We hit a case of CMS image uploads over-compressed. Troubleshooting started with logs on React Native, then followed our reproduction steps. Archive screenshots and config change IDs for this role-based access control round so next month's retrospective stays concrete. The same requirement can sound different across departments; writing it down helps align decisions on inquiry form conversion path. We hit a case of mobile menus nested too deep. Troubleshooting started with logs on a hosting panel, then followed our reproduction steps. Next, we recommend to document the reproduction path in a shared sheet. If more features are added, scope the blast radius before scheduling.

Testing & Acceptance

This write-up is for colleagues progressing website and CMS work. The client is in logistics & warehousing, roughly a hundred-person team, based around Southeast Asia. We hit a case of holiday traffic spikes slowing the site. Troubleshooting started with logs on Nginx, then followed our reproduction steps. 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 CMS publishing workflow. QA walked the main path three times on real devices and flagged edge cases around CMS publishing workflow. Next, we recommend to run a real-device smoke check before go-live. If more features are added, scope the blast radius before scheduling.

Delivery Approach

The same requirement can sound different across departments; writing it down helps align decisions on site performance optimization. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to site performance optimization first. Archive screenshots and config change IDs for this site performance optimization round so next month's retrospective stays concrete. Last week we reviewed company website development with the client's IT lead. They care more about stability than buzzwords. 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. This write-up is for colleagues progressing website and CMS work. The client is in home & building materials, roughly a dozen staff, based around free-trade zones. Editors know the CMS well enough, but inquiry form conversion path still needs a one-page rule sheet to cut verbal rework. Archive screenshots and config change IDs for this inquiry form conversion path round so next month's retrospective stays concrete.

Takeaways: The same requirement can sound different across departments; writing it down helps align decisions on brand site launch. QA walked the main path three times on real devices and flagged edge cases around brand site launch. Next, we recommend to temporarily disable noncritical plugins and retest. If more features are added, scope the blast radius before scheduling.