Web design for architects in Mallorca: a portfolio that explains before it impresses

A clearly presented selection of projects, useful filters, project profiles with context and decisions, information about the practice, services, contact details and authorship guidelines. It should also plan for image performance, accessibility, SEO, licences, credits, analytics and maintenance.

Not necessarily. A short, well-explained selection often provides better guidance than an indiscriminate archive. The rest can remain in a filterable archive or in specific dossiers. The decision depends on the type of client, the practice's track record and its objectives.

Only those that help people compare. The most common are type, status, scale, location or year, but they should not be added if they leave categories with a single project or require visitors to understand the practice's internal taxonomy.

Alongside images, it is useful to explain the commission or challenge, relevant constraints, the architectural decision, status, location at the authorised level of precision, the practice's role and credits. Area, budget or timescales are only published when they are verifiable and permission has been given.

With sizes adapted to their container, modern formats where appropriate, declared dimensions, reviewed compression and lazy loading below the first screen. Each asset needs a purpose: images show, captions provide context, and alternative text describes what is needed to understand it.

Yes, if art direction considers performance from the outset. Page weight depends on resolution, format, compression, number of assets, videos, fonts and scripts. The actual templates are tested on mobile; optimising an empty homepage is not enough.

Through a consistent entity and contact details, a clear service page, well-described projects and areas of work, internal linking and a properly managed Google profile. I do not recommend creating repeated local pages without a presence, content or a distinct proposition.

Only when there is enough material and a useful intention behind them. Housing, renovation, interiors, public facilities or urban planning may deserve their own pages if they help people decide and bring together projects, process and specific answers; not if they repeat the same text with one word changed.

With crawlable URLs for each language, editorial translation, a visible language selector, canonical tags and reciprocal hreflang. Proper names, credits and technical details must remain consistent. You also need to decide which projects and services are relevant to each market.

The practice must confirm what it can publish, in which media and for how long. The website must credit photographers, collaborators and authors according to the agreements, avoid unlicensed material and retain a record of permissions. Technical design does not replace that contractual validation.

With discreet, clear user journeys: explain who the practice works for, how a commission starts, what information it needs and the next step. A briefing form can qualify the enquiry without requesting unnecessary data or promising an assessment before reviewing the case.

The foundation can be shared, but each audience needs a different next step. A private client looks for fit and process; a competition team needs capabilities and documentation; a publication wants images, credits and details ready to cite. The architecture should offer these routes without duplicating everything.

It can, if that is part of the scope. First, we need to define who will publish, which fields will be mandatory, how images and credits will be handled and what permissions each user needs. An easy-to-use dashboard requires a clear editorial structure, not just installing a CMS.

There is no responsible figure without knowing the number of templates, projects, languages, migration requirements, art direction, content and integrations. After reviewing the material, I can propose phases, deliverables and an itemised quote, without presenting an automatic estimate as a binding offer.