Company website guide: site performance optimization for construction

Context: The same requirement can sound different across departments; writing it down helps align decisions on brand site launch. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to brand site launch first. Prefer a go-live window outside peak traffic, and prepare the rollback package early.

Delivery Approach

The same requirement can sound different across departments; writing it down helps align decisions on inquiry form conversion path. Editors know the CMS well enough, but inquiry form conversion path 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. This write-up is for colleagues progressing website and CMS work. The client is in healthcare, roughly a multi-division group, based around new urban centers. Editors know the CMS well enough, but basic accessibility 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.

Operations & Collaboration

Last week we reviewed brand site launch with the client's IT lead. They care more about stability than buzzwords. We hit a case of a teammate accidentally deleting a channel. Troubleshooting started with logs on CDN, then followed our reproduction steps. 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 role-based access control. We hit a case of CMS image uploads over-compressed. 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.

Risks & Mitigations

This write-up is for colleagues progressing website and CMS work. The client is in sports venues, roughly two hundred+ staff, based around high-tech zones. We hit a case of holiday traffic spikes slowing the site. 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 mobile responsiveness with the client's IT lead. They care more about stability than buzzwords. We hit a case of a teammate accidentally deleting a channel. Troubleshooting started with logs on object storage, then followed our reproduction steps. Add a field dictionary to the docs so new joiners ask fewer repeat questions.

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