Websites with a Growing Portfolio: Resolving an Unstructured Project List Before Drawing the First Layout

A growing portfolio needs a content structure before it needs a new grid. Start by deciding which work demonstrates the services you offer, how visitors will find relevant examples and what each project page must explain. That gives the layout a clear purpose as the collection expands.

An unstructured project list often mixes commissions, concepts, old capabilities and several naming systems. Publishing another row of thumbnails can make the problem larger. This guide explains how to audit the work, choose a maintainable structure and prepare a useful brief for a portfolio website redesign.

Audit the work before designing categories

Create an inventory of published projects and work being considered for publication. Give each project a stable identifier, its current URL, a clear working title and a short description of what you contributed.

Record the service demonstrated, project type, publication status, available images and any permissions or credits that need confirmation. Note missing context as well as missing files. Ten polished images do not explain whether you led the design, contributed one part or created a personal concept.

Keep the first pass factual. A project should not become “strategy” because that category needs another example. If the contribution is unclear, ask the person who can verify it before assigning the label.

This illustrative audit shows the kinds of decisions to capture. The entries are fictional, not SavianoDesign client work.

Project record	Useful evidence	Information gap	Editorial decision
Boutique hotel homepage concept	Hospitality layout and responsive design approach	Final small-screen views	Complete the missing views; label it as a concept
Commissioned product catalog	Information hierarchy and page design	Collaborator credit	Confirm the credit before publishing
Older studio identity	Logo development relevant to a current service	Low-resolution images	Retain if still representative; prepare suitable assets
Internal interface experiment	A focused interaction study	No full application exists	Publish as a clearly scoped study, if useful

The audit separates work that is ready, work needing an editorial update and work that does not support the current offer. It also prevents a redesign from silently dropping valuable pages simply because their images are inconvenient.

Decide what the portfolio needs to prove

Write the questions a prospective client brings to the work. They might need to assess a service, a type of project, a particular context or the way you explain decisions. Organize the selection around evidence that helps answer those questions.

Distinguish the public portfolio from the complete internal archive. The website can show a considered selection while keeping additional material available for a relevant enquiry. There is no universal number of projects that makes a portfolio persuasive.

For each current service, check whether the selected work offers a credible introduction and useful variation. Several nearly identical examples may add less than a smaller set that explains different constraints. Conversely, a single image should not imply an extensive record in a new specialty.

If clients and collaborators need different evidence, plan the two audience journeys before building separate portfolios. They may benefit from different selections linking to the same complete project pages.

Choose one principle for the main categories

Project collections can be organized by service, building type, subject, sector or another attribute meaningful to the audience. Choose one principal basis at each level. Mixing “Web Design,” “Hotels,” “2025” and “Experiments” as equivalent categories asks visitors to compare different kinds of information.

Other attributes can remain supporting details. A project may have a service category, a sector and a completion year without needing all three to appear as competing navigation choices.

Write a one-sentence rule for each proposed category: what belongs, what does not and which visitor question it answers. Assign the current projects using those rules. If the team repeatedly disagrees, the boundaries need work before the visual treatment begins.

For specialist examples, see organizing photography shooting specialties and grouping architecture project types. Both approaches begin with a meaningful organizing principle and keep secondary attributes in supporting roles.

A project can appear in several relevant collections while retaining one project page. Explain why it is relevant through the card description or selected image. Repeating the complete case study under several URLs adds maintenance without necessarily helping the visitor.

Separate featured work from the full collection

The homepage selection introduces the practice. A category selection demonstrates one part of the offer. The archive helps visitors explore more widely. Those positions do not need identical ordering.

Choose featured projects deliberately. A new publication may belong in the archive without replacing the strongest introductory example. The guide to choosing a representative first photography project offers criteria that also help other creative portfolios: relevance, clarity of contribution and the direction of work you want to attract.

Use “Selected work” when the page is intentionally curated. If the page promises a complete archive, make the remaining work reachable. Visitors should understand whether they are viewing highlights or the full published collection.

For projects from several cities, keep the place as project context unless geography is genuinely how clients choose the work. A project location does not establish a studio office there. The guide to organizing a multi-location website explains how to distinguish branch information from other geographic references.

Define a project page that makes the evidence useful

A useful case study identifies the brief, your role, the relevant work and the decisions needed to understand it. Add outcomes only where you can substantiate them. A concept can explain its design intention without claiming results from a business that never launched it.

Agree the minimum content before choosing the gallery layout: a descriptive title, short introduction, scope or contribution, selected images with context, credits where relevant and an appropriate next step. Some projects need additional sections; consistency should provide orientation without forcing every story into the same length.

Use headings that describe the actual sections. W3C’s headings tutorial explains that headings communicate organization and can support in-page navigation. In a case study, that means the section structure should remain understandable beyond its font sizes and visual spacing.

Describe informative images according to what they contribute. Avoid repeating a search phrase in every alternative text. If a screenshot demonstrates navigation, describe that relevant feature; use the surrounding caption or text for a longer explanation.

Add browsing controls when the collection needs them

A small number of clear category links may be sufficient. Filters become useful when visitors need to narrow a larger set using meaningful, consistently recorded attributes. First make the underlying categories reliable; a filter cannot resolve ambiguous project labels.

Specify how active filters are shown, cleared and preserved when a visitor returns from a project. Decide how an empty result is explained. If pagination is used, make later pages reachable and identify the current position in the archive.

Keep important categories and project pages linked with ordinary URLs. Google’s link guidance describes crawlable anchors and meaningful link text. A practical application is to give each published project a descriptive link instead of relying entirely on a visual state inside a script-driven grid.

During implementation, check long project names, narrow screens and keyboard use. Review image fitting by content type: a browser screenshot may need its full frame visible, while a photograph may tolerate a considered crop. Decide that behaviour explicitly before applying one image rule to every asset.

Write a rule for adding the next project

Ask what happens when the next commission arrives. Who writes the introduction, confirms the category and checks the assets? Who decides whether it becomes featured? Which service or existing project should link to it?

Use a short publication checklist based on the agreed project fields. That gives a contributor a repeatable process without requiring them to redesign the taxonomy for every addition. Review the structure when a genuine new service or body of work emerges, rather than creating a category for every exception.

Preserve useful URLs when changing display titles or category membership. If an old page must move, plan a direct redirect to the relevant replacement and update internal links. Do not send every retired project to an unrelated homepage merely to make the old address resolve.

Before approving the brief, test whether someone unfamiliar with the work can find a relevant example, understand your contribution and identify the next action. Hand the designer the inventory, category rules, featured selections, project outline and maintenance responsibilities.

Common questions

Should a growing portfolio show every completed project?

Only publish work that serves a clear purpose and that you can present accurately. A curated portfolio can remain convincing while the wider archive stays internal. Keep useful older work when it still demonstrates a service you offer.

Can a project belong to more than one category?

Yes, when it provides relevant evidence for each category. Usually those collection entries can link to one complete case study. Confirm that the labels help a visitor choose rather than describing the same capability in several ways.

When should a portfolio add filters?

When visitors need to refine a collection using meaningful attributes and simpler category links are no longer sufficient. The decision depends on the tasks and content, not a universal project-count threshold.

Shape your portfolio website with SavianoDesign

SavianoDesign’s Web Design service brings project organization, visual hierarchy and responsive case-study layouts into a complete portfolio website or redesign.

Browse the Web Design portfolio and contact Francesco about your portfolio. Share your current site, project list and the work you want to attract. Together we can define the structure, content priorities and agreed design or front-end deliverables.