WordPress website development

What a WordPress build covers

A typical project includes planning the pages and content types, choosing or building a theme, configuring the editor, adding the plugins needed for forms, search engine settings or other features, migrating or writing content, testing on different devices and browsers, and launching on hosting. After launch, someone has to apply updates, keep backups and watch for problems. A project that leaves out the after-launch part is only half planned.

The main parts and the decision each needs

Start with the content model

Before choosing a theme, list the kinds of content the site holds: service pages, case studies, team profiles, events, articles. For each, note the fields it needs, such as a date, a location or a summary. A site whose structure matches its content is easier to edit, search and redesign later. Forcing everything into generic pages tends to create inconsistency as the site grows.

Choosing a theme approach

A ready-made theme is quick to start with but may carry features you do not need and design limits you discover later. Customising a well-maintained theme can be a middle path. A theme built for the site fits exactly but needs someone to maintain it. Whichever approach is chosen, customisations should be made in a way that survives theme updates, so that updating does not overwrite changes.

Plugin discipline

Plugins add features, and each one is code that needs updating and can conflict with others. Before adding one, ask whether the feature is needed, whether the plugin is actively maintained and whether it overlaps with something already installed. Keep a list of every plugin, what it does and why it is there; that list makes maintenance and later redesigns far easier.

How a WordPress build usually runs

1. 01

   Discovery

   Goals, audiences, content types.

   Output: Content model and sitemap

2. 02

   Design

   Page templates and components.

   Output: Approved designs

3. 03

   Build

   Theme, editor setup, plugins.

   Output: Working staging site

4. 04

   Content

   Pages entered or migrated.

   Output: Complete staging site

5. 05

   Test and launch

   Devices, forms, speed, redirects.

   Output: Live site and handover notes

Example: a WordPress site for a surveying practice

Before you agree a WordPress build

The editing experience

The people who update the site daily matter as much as the visitors. Decide how much freedom editors should have: full control over layouts, or a set of approved blocks and templates that keep pages consistent. Short written guidance and a walk-through at handover help new editors avoid breaking layouts.

Hosting and responsibility

Because WordPress is self-hosted software, someone must choose the hosting, keep the server current and manage the domain and email settings. Agree in writing who owns the hosting account, who holds administrator access and who is responsible if the site goes down. The business should own its domain and hosting accounts, with access granted to whoever manages them.

Updates and backups

WordPress documentation recommends backing up before updating. Since version 3.7, minor and security updates can apply automatically in the background on most sites, while major releases are applied manually. Themes and plugins need updating too. A backup is only useful if it can be restored, so test a restore occasionally.

Speed and accessibility

Heavy themes, large images and many plugins can slow a site down. Optimised images, a lean theme and careful plugin choice help. Accessible templates, with proper headings, alt text, keyboard navigation and sufficient contrast, serve more visitors and are easier to build in from the start than add later.

Owning what is built

Agree that you own the content, the design and any custom theme code once paid for, and that you receive administrator access, a list of plugins and any licence keys for paid plugins or themes. Licences for premium plugins should ideally be in the business's name.