Building the Architect's Portfolio

Beyond the generic developer grid.

Most developer portfolios follow a predictable cadence: a dark-mode hero, a grid of cards, and a list of progress bars representing "skills." As a Digital Experience Architect, I found this format lacking. It treats software development as a commodity rather than a craft.

For my personal site, I wanted to build something that felt less like a dashboard and more like a high-end publication. I call this aesthetic "Editorial Tech." It is an attempt to bridge the gap between the rigid logic of functional programming and the fluid elegance of modern typography.

Bleeding edge tools for a zero-latency experience.

Choosing the right tools is the first act of architecture. I opted for Next.js 16 and Tailwind CSS v4—not just for the sake of being current, but for the specific performance gains they offer.

By leveraging Server-Side Rendering (SSR) and Incremental Static Regeneration (ISR), I ensured that every project page and blog post loads instantly. In an era where 500ms of latency can lose a user, my goal was an imperceptible "zero-wait" state.

Managing thoughts with Velite and MDX.

A blog shouldn't be a separate entity managed by a heavy CMS. It should be a part of the repository, governed by the same Clean Code standards as the UI.

I implemented Velite to handle my content pipeline. This allows me to write in MDX, treating my prose as code. Every paragraph is standard Markdown, but every case study or technical deep dive can import custom React components for interactivity.

Why this matters:

• Type Safety: My content is validated via Zod schemas during the build process.
• Performance: No external API calls to a headless CMS are required at runtime.
• Version Control: My thoughts and my code live in the same Git history, providing a unified timeline of my development as an engineer.

The math of color and type.

Architecture is often found in the details that users don't consciously notice but definitely feel.

Typographic Cadence

I chose Source Serif 4 for headings to provide an authoritative, intellectual weight. This is balanced by IBM Plex Sans for the body—a typeface designed to reflect the relationship between man and machine. It is a subtle nod to my USP: speaking the languages of humans and machines with equal precision.

The OKLCH Color Model

Instead of HEX or HSL, this portfolio uses the OKLCH color space. This allows for "perceptually uniform" brightness.

Logic meets Empathy.

This portfolio is more than a list of links. It is a reflection of my philosophy: that software should be as beautiful as it is functional, and as communicative as it is logical.

As we enter 2026, I am committed to exploring how we can use these tools—not just to build faster apps, but to build more meaningful digital experiences for the communities that need them most.

“

Software is the only medium where we can architect pure logic into human impact.