Theme and blocks
A block theme built to the approved designs, with reusable patterns for the sections your pages repeat. Colors, type and spacing live in one theme.json file, so a change is made once. You receive: the theme on a staging site, and the repository in your name.
The editor your staff use
Pages are edited in the block editor with the layout locked, so a staff member can change a headline or a photo without moving a section. Staff roles get only the access the job needs. You receive: an editing guide, and a login for each person who edits.
Plugins and hardening
Each plugin chosen for one job and recorded with the reason. Unused plugins and themes are deleted, the dashboard file editor is switched off, logins are limited and every admin account uses two-step sign-in. You receive: the plugin register and a hardening checklist.
Updates and the log
Core, theme and plugin updates are applied to a staging copy first, checked on every template and then released. An update that breaks a page is held back, and the log says why. You receive: the update log, with each entry showing what changed, where it was tested and the result.
Hosting and backups
A host chosen with you against WordPress’s published requirements, in an account in your name. Backups cover the database and the files, are kept in a second location and are restored once to a clean copy before launch. You receive: the hosting account, and a written restore record with the steps to repeat it.
Speed on a phone
Images sized on upload, a page cache and a short script list, measured on each template against the Core Web Vitals limits. A page that goes over is fixed before launch, or the scope says why it stays. You receive: the measured result for each template.