Website project retrospective: role-based access control (a hundred-person team)

Context: This write-up is for colleagues progressing website and CMS work. The client is in food & beverage, roughly around fifty employees, based around Europe. 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

The same requirement can sound different across departments; writing it down helps align decisions on mobile responsiveness. QA walked the main path three times on real devices and flagged edge cases around mobile responsiveness. 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 hospitality & travel, roughly a multi-division group, based around capital business districts. We hit a case of CMS image uploads over-compressed. Troubleshooting started with logs on approval workflows, 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 basic accessibility. 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.

Operations & Collaboration

The same requirement can sound different across departments; writing it down helps align decisions on static asset caching. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to static asset caching first. 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 channel & URL planning. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to channel & URL planning first. Add a field dictionary to the docs so new joiners ask fewer repeat questions.

Testing & Acceptance

Last week we reviewed basic accessibility with the client's IT lead. They care more about stability than buzzwords. Editors know the CMS well enough, but basic accessibility 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 landing page SEO basics. Editors know the CMS well enough, but landing page SEO basics 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. This write-up is for colleagues progressing website and CMS work. The client is in cross-border trade, roughly around fifty employees, based around Southeast Asia. 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.

Takeaways: The same requirement can sound different across departments; writing it down helps align decisions on company website development. Editors know the CMS well enough, but company website development 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.