Notes on lasting portfolios

A portfolio works best when it doesn’t depend on a single yearly overhaul. The trick is to make publishing a new project almost as easy as writing a note — and to make sure the system doesn’t break after two years of silence.

The non-negotiables

• Typed content. An explicit schema (zod, Sanity, whatever) so a new CMS field appears or fails in build, not in production.
• Consistent imagery. One dominant ratio for covers, one for stills, with size ranges served automatically. Without this, a portfolio feels uneven by month six.
• Per-page SEO. Title, description and canonical specific to each entry. If the CMS doesn’t allow it, fix it before publishing more.
• Automatic RSS and sitemap. Not glamorous, but they’re what lets your existing audience hear about it and search engines index without friction.
• A CMS without ceremony. An editor that opens in one click, doesn’t require code edits for editorial changes, and can be used by someone without context.

What ages well

Properly subsetted variable type, short palette, layout that doesn’t lean on the framework du jour. Animations restricted to specific moments. Optional video with respectful consent handling.

What ages badly

Carousels, heavy parallax in the hero, micro-interactions on every hover, autoplay video without compression. Everything that was “trending” two years ago and now weighs five times what it should.

A practical rule

Anything you add has to survive untouched for the next two years. If it can’t, it doesn’t ship. If it does, document how to remove it.