Folio 23

Most portfolios don’t scale well.

New projects get added over time, layouts start to break, and consistency becomes harder to maintain.

What starts as something clear eventually turns into a collection of pages that don’t quite relate to each other.

At the same time, there was no external constraint here.

Every decision — from structure to visuals to implementation — had to be defined from scratch.

I approached the portfolio as a system.

Instead of starting with layouts, the focus was on how content is structured and how it evolves over time.

Projects are defined as structured data using JSON, separating content from presentation.

This makes it easier to manage, update, and extend without changing the underlying system.

The interface is built using modular components.

Rather than fixed templates, layouts are assembled from reusable blocks that adapt to different types of content.

This allows each project to have its own structure without breaking consistency across the site.

A large part of the iteration focused on the hero section, which needed to communicate both visual identity and technical approach without adding unnecessary complexity.

The project was designed and developed entirely by me.

The system is built using:

• structured content managed through JSON
• a component-based architecture
• static generation with Astro

An earlier version relied on dynamic loading, but was later rebuilt to simplify the codebase and improve performance.

This resulted in a faster, more maintainable system where each project works as an independent page.

The result is a portfolio that works as a system, not just a collection of pages.

Projects are:

• easier to organize and maintain
• consistent without being rigid
• flexible enough to adapt to different types of work

New content can be added without redesigning the site.

The portfolio became both a design and development system, where the way projects are structured defines how the work is experienced.