A portfolio should explain the project as well as show it. Add context, responsibilities and permission-aware photography with a manageable mobile image load. Label an unbuilt concept clearly and describe its spatial approach rather than presenting renders as photographs of completed work. Attractive images do not justify publishing private client details or photographs without rights.
Select projects that explain the studio's work
A portfolio is an edited presentation, not a backup of every project photograph. Choose work that represents the services you want to discuss with future clients. For each selected project, gather its name, type, relevant scope, your role and a short explanation of the design problem. A visitor should understand more than the fact that an attractive space exists.
Keep participation precise. If the studio completed interior planning but not the building architecture, say so. If a project was collaborative, identify the role without implying sole authorship. Concept studies and unbuilt work can be included when clearly labelled; they should not be mixed with completed commissions in a way that misleads a reader.
Sequence projects intentionally. A first image may establish the overall space, while later images explain circulation, materials or a detail discussed in the text. Ten nearly identical views can make the page slower and the story weaker. The editorial question is what each image contributes, not how many images the gallery can display.
Confirm publication rights and mobile composition
Create a rights record for photographs, drawings and renderings. Note the creator, permitted use and any credit that must accompany publication. Obtain necessary permissions before assets enter the public folder. Removing a name from a plan does not necessarily make every detail appropriate for public release; review what the drawing actually reveals.
Then test how each important image crops at different screen sizes. A wide architectural composition may lose its subject when forced into a narrow card. Use an intentional crop for the card and a fuller image where the project is explained. Keep captions close enough to their images that mobile reading order remains understandable.
Prepare web-sized exports without discarding the originals. Detailed drawings may need a different treatment from atmospheric photographs. Check the actual page for unreadable labels, compression and unexpected layout movement. A large monitor in the studio is not a sufficient test of the mobile portfolio a prospective client may open during travel.
Connect visual work to a clear enquiry
The service pages should explain what the studio offers beyond the images: project stages, typical involvement and how an initial discussion begins. Avoid suggesting that a project can be priced accurately from a visual style alone. The site can help gather context while leaving detailed scope and professional responsibilities to the actual conversation.
A project enquiry might ask about the type of space, broad location and intended timing, without forcing the visitor to upload sensitive plans. If attachments are needed later, decide how they will be shared securely. A public introduction form does not need to become a document-management system on launch day.
Before approving the portfolio, follow one project from its thumbnail to its detail page and then to contact. Check that the return path is clear, image descriptions fit the content and the enquiry preserves relevant context. A well-designed portfolio helps the visitor appreciate the work and understand the studio's role. It does not need invented awards, client counts or measured performance claims to do that convincingly.
Build one complete project before filling the gallery. Choose an approved project and prepare its card, detail page, image sequence, credits and enquiry link. Review the entire sequence on a phone. This exposes decisions about crop, caption placement and navigation before those choices are repeated across the portfolio.
Ask whether every image has a reason to remain. One overview, a useful plan where publication is allowed and a few meaningful details may tell the story more clearly than many near-duplicates. Keep the original archive separate so editing the public selection does not discard material the studio needs privately.
When a project changes status from a study to completed work, update the wording deliberately. Do not let a status label or metadata remain inconsistent with the visible description. A portfolio evolves with the practice, so ownership of image rights, project text and future additions should be part of the handover. This keeps the site accurate as well as visually coherent and prevents the public archive from becoming an unmanaged collection of old exports.
Practical checklist
- State the project status
- Credit contributors when required
- Explain the design challenge
A concrete example: Label an unbuilt concept clearly and describe its spatial approach rather than presenting renders as photographs of completed work.
A boundary to keep clear: Attractive images do not justify publishing private client details or photographs without rights.
Your next step
Tell Orvunweb about your project
