Context before form
Proposition, audience, content and objectives are organised before a visual direction is set.
——
WordPress web designer in Barcelona: bespoke sites for brands that need autonomy, speed and a presence that matches their product.
WordPress
The approach is defined before it becomes a set of screens.
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.
Proposition, audience, content and objectives are organised before a visual direction is set.
Navigation, content and actions are shaped around the questions that arise throughout the journey.
The system is prepared so the team can maintain and extend it with sound judgement.
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.
Almost every company that arrives saying «our WordPress is slow» has the same installation: a purchased theme, a visual builder on top, thirty plugins and nobody who remembers why half of them were installed. WordPress is not the problem; that combination is. A bespoke WordPress removes the builder, cuts plugins down to the ones genuinely needed and builds the blocks that business actually uses each week. The editor ends up with fewer options and more sense, and the site stops breaking every time somebody publishes.
The question to answer before writing any code is not what can be edited, but what should be editable. A client who can change everything eventually breaks the grid by accident; one who can change nothing calls about every phone number. The middle ground is decided case by case: specific fields for what changes often, locked down for what holds the design together. It is a product decision, not a technical setting, and it separates a site that ages well from one that degrades within six months.
Many WordPress projects in Barcelona are not new sites: they are installations with years of content, positions earned in Google and forms wired to something. Rebuilding from scratch is the fastest way to lose that history. The work starts with an inventory of URLs, content and assets, and a mapping plan, before anyone touches the design. The dull part of a migration is exactly where traffic is won or lost.
Not resolved — gathered. The current site, who you are addressing, what you offer, what material exists and who decides. The first phase separates what blocks progress from what can be settled while building.
By journeys and decisions, not by number of screens. We agree what a person has to be able to do, what content supports it and what stays out of this phase. That is what gets costed.
Less than feared, but at specific moments. Two or three decision sessions and access to whoever knows the business. The rest moves forward without status meetings that decide nothing.
The journeys that matter are tested on mobile and desktop, along with forms, real-world speed, accessibility and anything that has moved since the previous site. The checklist comes from the scope, not from a generic template.
By the quality of the enquiries that arrive and by what the team manages on its own. More traffic without better conversations is not an improvement, and it is worth saying so up front.
You get documentation on how each part is edited and a prioritised list of what was deferred. From there, either the team runs it or we agree a phased follow-up.
A selection of work showing context, decisions and outcomes.
Tell us where things stand and we can assess the most useful approach for the project.
