Portfolios

2.6.1Definition & Purpose

A portfolio site exists to showcase a specific body of work — design, writing, code, photography — to an audience evaluating the creator, typically for hiring or commissioning purposes. Its entire structure should serve fast, credible evaluation of the work, not general self-expression for its own sake.

2.6.2Architecture Priorities

Almost always static. Image and media optimization matters disproportionately here, since visual and creative portfolios are asset-heavy by nature — unoptimized media is the most common cause of a portfolio feeling slow despite simple structure.

2.6.3UX Priorities

• Work should be reachable within one or two clicks from the homepage — don't bury the actual portfolio behind extensive narrative framing.
• Each piece needs enough context (role, problem, outcome) for an evaluator to judge it without needing to ask.
• Contact information must be effortless to find — a portfolio's ultimate call-to-action is almost always "get in touch."

2.6.4Common Mistakes

• Showcasing volume over relevance — including every project ever made rather than a curated set aligned with the audience being targeted.
• Heavy, unoptimized media assets that make the site itself feel like poor craftsmanship, undermining the work it's meant to showcase.
• No context per project, leaving evaluators unable to tell what the creator actually contributed versus a team.

2.6.5Best Practices

• Curate ruthlessly toward the specific audience the portfolio is meant to reach.
• Compress and lazy-load imagery; a portfolio's own performance is itself a demonstration of craft.