BCN —:— Diagnostic
[ Overview ]

WordPress website maintenance

Technical and ongoing maintenance so a website remains fast, secure and useful after launch.

Maintenance

[ Overview ]

The approach is defined before it becomes a set of screens.

What it needs to solve
WordPress website maintenance

The project starts with the decision the digital presence needs to support, the information behind it and the operations the team needs to sustain. This way, design and technology respond to a specific need.

[ A clear way of working ]

A clear way of working

01

Context before form

Proposition, audience, content and objectives are organised before a visual direction is set.

02

Structure that supports

Navigation, content and actions are shaped around the questions that arise throughout the journey.

03

A foundation that evolves

The system is prepared so the team can maintain and extend it with sound judgement.

[ Overview ]

Let’s discuss the project

  • Analysis of context, audience and starting point
  • Information architecture and content priorities
  • Visual direction, interface and development
  • Measurement, maintenance and ongoing evolution
[ For this assignment ]

WordPress website maintenance

Strategy, content, design and implementation are organised around the organisation’s context. Decisions are documented so the team has a clear foundation for launch, maintenance and future development.

[ Related project ]

Allergy Therapeutics Ibérica 2026

View the project ↗
[ FAQ ]

Before deciding

What is needed to start?

Access and an inventory of what exists: hosting, domain, plugins, integrations and who has touched what. The first audit usually turns up dependencies nobody remembered.

What exactly does WordPress website maintenance include?

Updates tested before they are applied, verified backups — a backup never restored is not a backup — uptime monitoring and an incident channel with agreed response times.

What falls outside maintenance?

New development and redesigns. They are kept separate on purpose, so maintenance does not become a pot of hours where the urgent eats the preventive.

How do you know everything is still fine?

Through periodic reviews of performance, security, forms and server errors, plus a report that reads clearly without being technical: what was done, what was found and what needs deciding.

How is the result measured?

In incidents that never happen and response time when they do. It is a service you notice by its absence, which is why the work is reported.

Can the service be ended at any time?

Yes, and access, documentation and current state are handed over without holding anything back. Maintenance that survives only because nobody else understands the install is not a service, it is a dependency.

[ Related work ]

Related work

A selection of work showing context, decisions and outcomes.

Mantenimiento Planificado
Mantenimiento Planificado
Consulte su vacuna
Consulte su vacuna
[ Where to go next ]

What usually comes next

[ Let’s discuss the project ]

Let’s discuss the project

Tell us where things stand and we can assess the most useful approach for the project.