Stack and front end
The approved designs built as templates that work from a phone up to a wide desktop, on the platform we recommended in the scope. We keep plugins and dependencies few and list each one with the reason it is there. You receive: the built templates on a staging site, and a list of every plugin or package with its purpose.
Structure and modules
Pages, posts, forms, search and any store built as separate parts that can be changed one at a time, so adding a section later doesn’t mean rebuilding the site. You receive: a one-page diagram of the parts and how they connect.
CMS and integrations
A CMS your staff can edit without us, with layout locked, and connections to the systems you already run, such as a CRM, a booking tool, payments and analytics. Each connection is tested with a real submission. You receive: an admin login, a short editing guide and a test record for each integration.
Performance budgets
Limits set before the build for page weight, scripts and the three Core Web Vitals, then checked on every template as it is built. The scope says what happens when a page goes over budget. You receive: the budget sheet, and the measured result against it for each template.
Accessibility testing
Each template tested with a keyboard alone, with a screen reader and with automated checks, against WCAG 2.2 AA. Automated tools catch some issues and miss others, so the keyboard and screen reader passes are done by hand. You receive: a written test record, each issue with its fix.
Staging, launch and handover
A staging site for releases, as the scope specifies, a redirect from each old URL to its closest new page tested before launch, and a deploy you can repeat from the runbook. The accounts are in your name throughout. You receive: the repository, the redirect map, a README and a runbook.