The useful answer
An architecture website should connect a project’s brief, constraints and design response with carefully chosen visual evidence. It also needs to help a prospective client understand the practice’s role, services and way of working.
Reviewed · BeyondPHP
Edit projects as coherent stories
Select a small set of photographs, drawings and captions that explain each project. Include location at an appropriate level, project stage and the practice’s contribution. Identify collaborations and credits accurately. Unbuilt proposals and completed work need distinct labels so that visual polish does not imply a delivered commission.
Protect the experience of the imagery
Large visual assets deserve responsive sizing, sensible compression and readable captions. Galleries should work with touch and keyboard controls, while essential information remains available without motion. A visitor comparing practices should not need to wait for a film to finish before reading the project brief or finding a contact route.
Explain how a new commission begins
Describe the kinds of projects the practice undertakes and the first conversation it needs. Separate design services from construction delivery where responsibilities differ. Avoid asking clients to disclose detailed budgets or private property information in an initial public form. A focused introduction can lead to a more appropriate private consultation.
A practical next step
What to prepare.
- Project credits
Confirm authorship, collaborators, photographer credits and publication permissions.
- Selection rationale
Choose work that demonstrates the commissions the practice wants next.
- Practice profile
Approve service scope, team information and the enquiry process.
Questions worth asking.
Can we show unbuilt projects?
Yes, with clear proposal or concept labels and an accurate account of the practice’s role.
Will image quality suffer?
We prepare appropriately sized versions and review the visual result rather than applying one aggressive setting to every photograph.
Do we need dozens of projects?
A concise, well-explained selection can communicate more than a large archive without context.
