Web development with WordPress

Services, team members and case studies should not become one unstructured text field. Define content types, shared taxonomies and reusable fields. Link a case study to a service instead of copying it across landing pages. Before content entry, agree required fields, editor permissions and the rules for inclusion in listings.

Acceptance check
A related case study is updated in one record.

Build a design-specific set of blocks: opening section, facts, projects, team and enquiry. Editors change content and approved variations while the grid and typography remain consistent. Test long headings, missing images and reordered sections. Allow unrestricted HTML only where it is actually needed and the access implications are understood.

Acceptance check
Reordering blocks preserves the mobile layout.

Separate presentation from functions that must survive a theme change. Content types and integrations usually belong in a project plugin; templates and visual styles belong in the theme. Do not modify core or third-party extension files. Record each external plugin’s purpose, licence, update source and compatibility-testing owner.

Acceptance check
Changing themes does not remove content types.

An author can prepare content without permission to change site settings. Editors review and publish; administrators manage configuration. Assign capabilities rather than relying solely on role labels. A draft preview must not become a publicly accessible page. Agree who may change URLs, delete records and upload files.

Acceptance check
An author cannot change site settings.

Use structured attributes and clear filters for service catalogues. Title search, industry filtering and related case studies serve different needs. Avoid loading every record on every request as the collection grows. Test empty results, multiple result pages and preservation of the selected filter when returning from a detail page.

Acceptance check
An empty result has a clear explanation.

Collect only the required information and show a clear result. Validate on the server, protect the handler against abuse and keep CRM credentials out of the browser. REST API integrations need controlled response fields and write permissions. A CRM outage should not silently lose an enquiry: retain a delivery log and retry path.

Acceptance check
A CRM failure retains the enquiry in the log.

Size images for their display area and defer heavy media below the opening screen. Public-page caches must not contain personal data. Map redirects when permalink structures change. Verify titles, descriptions, canonical links and structured data on the finished site: installing an SEO plugin does not replace this work.

Acceptance check
The card does not shift as its image loads.

Test core, theme and plugin updates on a staging copy first, including editing, forms, search and critical templates. Back up both database and files and verify restoration. Hand over block descriptions, publishing instructions and an extension inventory. Agree update frequency and incompatibility handling rather than promising that failures can never occur.

Acceptance check
The backup restores media as well as data.