Website project retrospective: CMS publishing workflow (a dozen staff)

Context: This write-up is for colleagues progressing website and CMS work. The client is in hospitality & travel, roughly a multi-division group, based around capital business districts. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to HTTPS and certificate renewal first. Archive screenshots and config change IDs for this HTTPS and certificate renewal round so next month's retrospective stays concrete.

Risks & Mitigations

The same requirement can sound different across departments; writing it down helps align decisions on mobile responsiveness. We hit a case of payment succeeded but orders still pending. Troubleshooting started with logs on WeChat DevTools, then followed our reproduction steps. Archive screenshots and config change IDs for this mobile responsiveness round so next month's retrospective stays concrete. This write-up is for colleagues progressing website and CMS work. The client is in construction, roughly a dozen staff, based around East Asia. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to site performance optimization first. Next, we recommend to run a real-device smoke check before go-live. 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 hospitality & travel, roughly a hundred-person team, based around county-level cities. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to mobile responsiveness first. Next, we recommend to lazy-load homepage assets by route. If more features are added, scope the blast radius before scheduling.

Operations & Collaboration

Last week we reviewed inquiry form conversion path 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 inquiry form conversion path. Archive screenshots and config change IDs for this inquiry form conversion path round so next month's retrospective stays concrete. 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. Add a field dictionary to the docs so new joiners ask fewer repeat questions.

Testing & Acceptance

The same requirement can sound different across departments; writing it down helps align decisions on brand site launch. Editors know the CMS well enough, but brand site launch still needs a one-page rule sheet to cut verbal rework. Archive screenshots and config change IDs for this brand site launch round so next month's retrospective stays concrete. The same requirement can sound different across departments; writing it down helps align decisions on channel & URL planning. QA walked the main path three times on real devices and flagged edge cases around channel & URL planning. Next, we recommend to compare staging vs production configuration diffs. 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 brand site launch. QA walked the main path three times on real devices and flagged edge cases around brand site launch. Add a field dictionary to the docs so new joiners ask fewer repeat questions.

Background & Goals

Last week we reviewed basic accessibility 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 basic accessibility first. Archive screenshots and config change IDs for this basic accessibility 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 around fifty employees, based around Europe. We hit a case of a teammate accidentally deleting a channel. Troubleshooting started with logs on WeChat DevTools, then followed our reproduction steps. Archive screenshots and config change IDs for this image weight control round so next month's retrospective stays concrete. This write-up is for colleagues progressing website and CMS work. The client is in finance & tax consulting, roughly a dozen staff, based around coastal tech hubs. 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 property & industrial parks, roughly a dozen staff, based around high-tech 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.