Defined content and components
Prepare templates and fields around material and recurring tasks.
——
WordPress web design in Barcelona, combining a visual identity of your own with editing your team can understand. We design around your real projects, services and content. Your website should look the part and let you get on with your work.
WordPress
A corporate website project starts from €6,000. The proposal defines design, development, content and launch. Languages, migration and integrations are priced against the agreed scope.
I’m Jordi Ensenyat, founder of Code Barcelona. Explore the published projects to see how I work, or tell me what your website needs. References offer ideas; your project deserves a direction of its own.
To choose an approach, compare custom WordPress and a pre-built theme. For budget planning, see custom WordPress website costs for 2027, covering design, content, migration and editing.
Design and the editorial model need to work together.
A WordPress project combines interface and publishing: which pages exist, which data is editable and who maintains content. Editing is tested with representative material, while theme, extensions and integrations are reviewed. The proposal specifies implementation and team handover.
Prepare templates and fields around material and recurring tasks.
Test updates, translations and publishing with the people who will use the system.
Agree updates, support, access and recovery according to scope.
Bring representative pages and content, languages, editing tasks and extensions or systems to retain. The budget separates design, theme, migration, integrations and recurring services. The CMS name does not replace those decisions.
Templates are reviewed using real text, images and data, including extensive content and language versions. This tests whether structure supports the material the team will maintain.
Tasks and fields are agreed before development. Handover demonstrates updates and changes requiring support; installing WordPress alone does not establish editorial autonomy.
For an existing website, identify pages, content and addresses to retain or change. Transition includes link and contact checks. Migration alone does not guarantee preservation of all search positions.
Theme, extensions, hosting and connections have responsibilities and costs that belong in the proposal. Updates and support are agreed alongside handover tests and documentation.
Each resource helps define a different part of the brief. Review scope and project examples before deciding.
Editing tasks are defined in the brief and demonstrated at handover. Training is prepared and the team’s changes are distinguished from those requiring support.
The proposal states the design and implementation approach, components and editing limits. The choice follows content, functions and project needs.
Content, addresses, functions and dependencies are reviewed before migration is defined. The budget identifies what stays, what changes and how transition is checked.
It should specify updates, backups, recovery, support and owners according to the agreed service. These are not assumed to be included in initial development.
Bring the current website, pages, content, languages, editorial tasks and connected systems to separate design, implementation, migration and integrations using the same assumptions.
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.
