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

Context: Last week we reviewed mobile responsiveness 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 mobile responsiveness. Add a field dictionary to the docs so new joiners ask fewer repeat questions.

Operations & Collaboration

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 mobile menus nested too deep. Troubleshooting started with logs on Postman, 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 cross-border trade, roughly a dozen staff, based around historic downtown districts. Editors know the CMS well enough, but basic accessibility 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.

Background & Goals

The same requirement can sound different across departments; writing it down helps align decisions on HTTPS and certificate renewal. QA walked the main path three times on real devices and flagged edge cases around HTTPS and certificate renewal. 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 HTTPS and certificate renewal. QA walked the main path three times on real devices and flagged edge cases around HTTPS and certificate renewal. Archive screenshots and config change IDs for this HTTPS and certificate renewal round so next month's retrospective stays concrete.

Risks & Mitigations

Last week we reviewed inquiry form conversion path with the client's IT lead. They care more about stability than buzzwords. Editors know the CMS well enough, but inquiry form conversion path 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 restaurant chains, roughly a dozen staff, based around new urban centers. 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. 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. 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 brand site launch. We hit a case of mini program review rejected. Troubleshooting started with logs on CDN, then followed our reproduction steps. Archive screenshots and config change IDs for this brand site launch round so next month's retrospective stays concrete.