Show the work at the right scale.
A project can include photography, plans, material details and contextual views. The page should help a reader move from the overall idea into those details. Credits, project status and the practice’s role should be clear, especially for collaborative or unbuilt work.
Make the practice understandable.
Describe the kinds of projects you undertake, how you approach a brief and which stages you support. Keep qualifications and professional affiliations accurate. A prospective client should be able to understand your role without needing familiarity with architectural terminology.
- Project typology and status filters
- Photography, drawing and caption systems
- Practice process and service scope
- Brief-led enquiry routes
Protect the portfolio on small screens.
Wide drawings and carefully composed photographs need deliberate mobile treatment. Provide readable captions and avoid forcing text over busy imagery. Optimised images and sensible sequencing allow visitors to inspect the work without downloading every original asset at once.
Bring design thinking into search.
Short project descriptions can explain constraints, context and intent while helping search systems understand the work. Link typologies to relevant services and practice information. Avoid unsupported awards or performance claims; original reasoning is more useful than borrowed prestige.
Questions worth asking.
Can we include unbuilt work?
Yes. It should be clearly labelled as a proposal, competition entry or concept, with accurate authorship and project status.
Can the site support a small practice?
Yes. A focused selection of well-explained projects can be more useful than a large archive without context.