Web development in Girona, from design to a working website
A good interface needs an implementation that does it justice. We develop websites with attention to what users see and what teams need to maintain them: consistent components, editable content where necessary and a carefully prepared launch. From Girona, we collaborate on complete projects and implement designs that already have a defined direction.
From screens to a working system
Before development, we review pages, states and behaviours. A design also needs to explain what happens when an image is missing, text grows, a form has an error or someone navigates with a keyboard. Resolving these situations helps avoid important decisions appearing unexpectedly at the end of the project.
Development may cover a corporate website, launch page, portfolio or interactive experience. Content management systems, catalogues and integrations are evaluated against real needs. We choose the solution with its complexity, dependencies and future maintenance responsibilities in mind.
Performance and adaptation to every screen
We review image weight, font loading and the cost of video and animation. The aim is to preserve the visual direction while reducing waiting times and unexpected layout movement. Measurements help identify what should be improved and the trade-offs each resource brings.
The mobile version is treated as a complete experience. We adapt menus, layout, reading and touch interactions, and review intermediate screen sizes. We also check visible focus, labels and controls so essential functions do not depend solely on a mouse or an animation.
SEO in the code and an organised launch
The technical structure should make content understandable and indexable. We work on semantic HTML, metadata, links, canonicals, sitemaps and crawling rules according to the website. In multilingual projects, we connect the versions of each page correctly and avoid different routes competing over the same content.
Before publication, we review the main journeys, forms and domain configuration. When replacing an existing website, we agree redirects and how to handle its URLs. Handover specifies access, dependencies, documentation and responsibilities: hosting and maintenance are defined within the scope.
How we work
Technical review
We compare the design with functionality, content, integrations and constraints. We agree what will be built and how it will be checked.
Implementation
We build components and pages, connect the planned services and review the result with representative content.
Validation
We test the agreed journeys, mobile layouts, keyboard navigation and technical SEO configuration.
Launch
We publish the approved version and check the website on its domain. We document the handover and next maintenance steps.
What the project can include
- Responsive mobile and desktop implementation
- Agreed components and behaviours
- Defined content management or integrations
- Technical SEO configuration
- Performance and core functionality review
- Publication and handover documentation
Budget and scope
Budget depends on page templates, states, languages and integrations. We also specify content migration, external services, hosting and support. E-commerce features or private areas need their own definition.
Digital experience references
Vira and Galeón show interface and digital product work. Their cases illustrate the design approach; the development scope for your website is defined specifically in the proposal.
Frequently asked questions
Can you develop an existing design?
Yes. We first review the design file, mobile versions and intended behaviour. If states or functional decisions are missing, we identify them before confirming the scope.
Which technology do you use?
The choice depends on content, functionality and the team's ability to maintain the website. We explain the options and their implications before deciding; the tool should serve the project.
Is maintenance included?
Launch and maintenance are phases specified in the proposal. We agree what updates, support and future changes the website will need and who is responsible for each part.
Do you guarantee a speed score?
We define objectives and measure performance to guide improvements. Results vary with content, integrations, device and connection. Testing helps agree priorities without treating one score as the only measure of quality.
Tell us what you want to build
We can start with your design, your current website or a list of needs that still requires a clear structure.
Discuss web development