Website project retrospective: product-site information architecture (a multi-division group)

Context: Last week we reviewed landing page SEO basics with the client's IT lead. They care more about stability than buzzwords. Editors know the CMS well enough, but landing page SEO basics still needs a one-page rule sheet to cut verbal rework. Next, we recommend to run a real-device smoke check before go-live. If more features are added, scope the blast radius before scheduling.

Risks & Mitigations

Last week we reviewed company website development with the client's IT lead. They care more about stability than buzzwords. We hit a case of mini program review rejected. 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. This write-up is for colleagues progressing website and CMS work. The client is in logistics & warehousing, roughly around fifty employees, based around free-trade zones. QA walked the main path three times on real devices and flagged edge cases around brand site launch. Archive screenshots and config change IDs for this brand site launch round so next month's retrospective stays concrete. Last week we reviewed multilingual website build 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 multilingual website build first. Add a field dictionary to the docs so new joiners ask fewer repeat questions.

Background & Goals

This write-up is for colleagues progressing website and CMS work. The client is in sports venues, roughly a multi-division group, based around economic development zones. Editors know the CMS well enough, but product-site information architecture 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. QA walked the main path three times on real devices and flagged edge cases around image weight control. Add a field dictionary to the docs so new joiners ask fewer repeat questions. The same requirement can sound different across departments; writing it down helps align decisions on company website development. We hit a case of payment succeeded but orders still pending. 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.

Operations & Collaboration

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. Archive screenshots and config change IDs for this image weight control round so next month's retrospective stays concrete. 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. Next, we recommend to temporarily disable noncritical plugins and retest. 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 dozen staff, based around Europe. QA walked the main path three times on real devices and flagged edge cases around inquiry form conversion path. Add a field dictionary to the docs so new joiners ask fewer repeat questions.

Takeaways: Last week we reviewed basic accessibility 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 SSL certificates, then followed our reproduction steps. Add a field dictionary to the docs so new joiners ask fewer repeat questions.