Website project retrospective: HTTPS and certificate renewal (a hundred-person team)
{pboot:if('Context: Last week we reviewed search indexing diagnostics with the client's IT lead. They care more about stability than buzzwords. Editors know the CMS well e'!='')}Context: Last week we reviewed search indexing diagnostics with the client's IT lead. They care more about stability than buzzwords. Editors know the CMS well e
{/pboot:if}Context: Last week we reviewed search indexing diagnostics with the client's IT lead. They care more about stability than buzzwords. Editors know the CMS well enough, but search indexing diagnostics still needs a one-page rule sheet to cut verbal rework. Archive screenshots and config change IDs for this search indexing diagnostics round so next month's retrospective stays concrete.
Operations & Collaboration
Last week we reviewed HTTPS and certificate renewal 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 Git, then followed our reproduction steps. Prefer a go-live window outside peak traffic, and prepare the rollback package early. Last week we reviewed landing page SEO basics 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 landing page SEO basics first. Prefer a go-live window outside peak traffic, and prepare the rollback package early.
Risks & Mitigations
This write-up is for colleagues progressing website and CMS work. The client is in agritech, roughly around fifty employees, based around East Asia. We hit a case of holiday traffic spikes slowing the site. 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. The same requirement can sound different across departments; writing it down helps align decisions on channel & URL planning. Editors know the CMS well enough, but channel & URL planning still needs a one-page rule sheet to cut verbal rework. 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 image weight control. We hit a case of mobile menus nested too deep. Troubleshooting started with logs on object storage, then followed our reproduction steps. Next, we recommend to lazy-load homepage assets by route. If more features are added, scope the blast radius before scheduling.
Background & Goals
The same requirement can sound different across departments; writing it down helps align decisions on channel & URL planning. Editors know the CMS well enough, but channel & URL planning 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 company website development. Editors know the CMS well enough, but company website development still needs a one-page rule sheet to cut verbal rework. Next, we recommend to give editors a one-page publishing guide. 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 construction, roughly a hundred-person team, based around new urban centers. QA walked the main path three times on real devices and flagged edge cases around corporate website redesign. 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 landing page SEO basics. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to landing page SEO basics first. Next, we recommend to require a change request for any scope change. If more features are added, scope the blast radius before scheduling.