How to Organize Project Types on Architecture Practice Websites

Organize project types on an architecture practice website around the distinctions prospective clients use to find relevant work. Choose one clear basis for the main categories, keep project status and the practice’s role visible, and give each project a complete page. Add filters when they help people refine a substantial collection.

A portfolio should let someone move from “Do you work on projects like mine?” to an example that answers the question. A beautiful grid becomes more useful when its labels, captions and project pages explain what the visitor is seeing.

Start with a project inventory

Before choosing filter labels, list the work available to publish. Record what the project was, the practice’s contribution, its status and the material you can show. This often reveals that the archive needs better descriptions before it needs a more elaborate interface.

A compact inventory might include the following fields:

Field	What to record	How it helps the website
Building use or sector	Residential, workplace, cultural or another accurate description	Suggests the main project group
Type of intervention	New building, extension, refurbishment or reuse	Offers a second way to compare work
Project status	Completed, in progress, unbuilt proposal or competition entry	Establishes what the imagery represents
Practice’s role	The actual appointment or contribution	Makes experience and authorship understandable
Location and date	Publishable geographic context and relevant year	Helps visitors interpret the project
Available evidence	Photographs, drawings, descriptions and credits	Shows whether a complete case study is ready

Use internal notes for uncertainties and missing permissions. Do not fill gaps with a more impressive category or imply that an unbuilt project has been completed. A smaller archive with accurate context can communicate the practice more clearly than a large set of unexplained images.

Choose one basis for the main categories

An architecture portfolio can be organized by building use, project scale or type of intervention. The appropriate choice depends on the practice’s work and the questions its clients bring.

A multidisciplinary practice might use categories such as Residential, Workplace and Cultural. A residential specialist might find New Homes, Extensions and Renovations more useful. These are examples to test against the inventory, not a universal menu every architecture website should copy.

Avoid mixing several kinds of label in one row. “Residential,” “Completed,” “Interiors” and “London” describe different dimensions. A visitor cannot easily tell whether selecting one excludes the others or changes the meaning of the collection.

The website navigation planning guide offers a useful starting point: define the visitor’s task, choose predictable labels and make the destination match the choice.

Keep project categories separate from service stages

A project category tells a visitor what kind of work they are looking at. A service or process page explains what the practice can be appointed to do. These subjects should connect, while retaining their own purpose.

For example, a completed residential building may demonstrate several parts of the process, but its presence in the archive does not establish that every future commission includes all those stages. Explain the actual contribution on the project page, then link to the relevant service or process information.

The guide to explaining architectural design stages before the first meeting shows how to describe those responsibilities without making the portfolio carry the entire scope explanation.

Give projects one complete home, even when they fit several groups

A mixed-use building may be relevant to more than one audience. A house extension may also demonstrate work with an existing structure. It is reasonable for the same project to appear in more than one relevant collection.

Keep those entries linked to one complete project page. Do not create near-identical case studies simply to give the project a different category label. The page can explain all the meaningful aspects together, with one clear account of the role, status and work.

If a project does not fit comfortably, first ask whether the category structure is too narrow. An occasional exception may need a useful tag rather than a new top-level section. Empty categories and a growing “Other” group are signs that the structure needs another look.

Write project cards that provide context before the click

A project name may mean little to someone who has never encountered the practice. Support it with a concise description of the work and a visible status where needed.

For example, illustrative project-card copy could read: “Courtyard House — extension to an existing home · completed.” A separate caption or case study can establish the location and role. Adapt the wording to the real project; do not use a fictional example as portfolio evidence.

Keep image proportions and text placement consistent across the grid. Choose a view that communicates the project at card size, and check that a crop does not remove its defining feature. Plans or drawings may need a different presentation from photographs to remain legible.

Use a visible title that links to the case study. Important context should remain available without hover, including on a phone. A row of atmospheric images with hidden names makes comparison unnecessarily difficult.

Add filters only when the collection needs them

For a small archive, clear sections and an overview of all work may be enough. Filters become useful when visitors have enough projects to narrow down and the available distinctions reflect real questions.

Decide what selecting a filter means. Are people choosing one sector at a time, combining a sector with a status, or opening a separate category page? Make the active choice visible and provide a straightforward way to return to all projects.

During implementation, check keyboard access, focus visibility, touch operation and how updates are communicated to people using assistive technology. Keep controls understandable when labels wrap on a narrow screen. A visually compact filter bar is not useful if its selected state is unclear.

If a combination returns no projects, explain the situation and offer a reset. The guide to empty, error and loading states covers how to give people a recovery route instead of a blank grid.

Make category pages useful destinations

A dedicated category page earns its place when it helps someone understand that area of work. A short introduction, relevant projects and a link to the appropriate service can provide a coherent route for a prospective client.

If the archive contains only a few projects, an anchored section may serve the same purpose with less repetition. Avoid producing many thin category pages whose only difference is a keyword in the title.

Use ordinary links to reach important project and category pages. Google’s guidance on crawlable links explains how links with real destinations support discovery and how descriptive anchor text supplies context. Filters can improve browsing, while the underlying project pages remain accessible through the archive.

Use the case study to complete the explanation

A useful project page answers the questions the card cannot: what the brief involved, which constraints mattered, what the practice contributed and what the work currently represents. Select images that support those explanations rather than adding every available view.

Keep the facts consistent between the card and the case study. If the work was a competition entry, that status should survive the click. If imagery includes both a proposal and a completed phase, caption them so the difference is apparent.

Finish with another genuinely relevant project, a process explanation or a contact route. The companion guide to explaining an architecture practice’s expertise without jargon can help turn those facts into a clear account of the studio’s strengths.

Test the categories with real browsing tasks

Ask a reviewer to find a project similar to a brief you actually receive. Then ask them to identify whether it was built and what the practice did. Avoid telling them which filter or label to choose.

Repeat with a second task that uses a different distinction, such as finding work with existing buildings. Notice whether people interpret the category names as intended, whether a project appears where expected and whether returning to the archive preserves their sense of place.

Review the structure when new work is added. A category that once contained one project may become important; another may no longer reflect the practice’s focus. Consistent records make that decision easier than classifying every new image from scratch.

Common questions

Should an architecture portfolio be organized by sector or project type?

Choose the distinction that best matches the work and the intended client’s questions. A broad practice may benefit from sectors; a specialist may need more precise types of intervention. Test the labels with representative tasks.

Can one project appear in multiple categories?

Yes, when the relationships are meaningful. Use the same project page as the destination and explain the full context there, rather than creating duplicate case studies.

Do unbuilt projects belong in the portfolio?

They can show relevant thinking and skills when their status, authorship and context are clear. Separate proposal imagery from evidence of completed work and avoid claims the project cannot support.

Make your architecture portfolio easier to explore

SavianoDesign’s Web Design service can help organize project categories, build consistent case-study layouts and create a responsive route from selected work to an enquiry.

Contact Francesco about your practice’s website with your current portfolio, the types of work you want to emphasize and a sample of the project material available. Those inputs help define a clear structure before the visual design begins.