Building the Design Shell: Notes on Crafting My Portfolio

Building the Design Shell

I wanted a portfolio that felt like an extension of how I work, not just a gallery of finished pieces.

Most portfolios are polished and static. They show the end result but hide the thinking. I decided to build something closer to a working environment a design shell that feels alive, slightly technical, and open to exploration.

Why a terminal interface

The terminal format wasn’t just an aesthetic choice. It reflects the way I move between design and development. I often start in a blank space, type a few commands, and gradually shape the work. The interface on this site mirrors that process.

It also creates a small moment of interaction before the work appears. Visitors who type `site` or `help` are already engaging, even if only lightly. That small friction feels more honest than a fully passive scroll.

Design + development + storytelling

My work sits at the intersection of three things:

• Graphic design — visual systems, composition, typography, and identity
• Full-stack development — building functional interfaces and experiences
• Multimedia — motion, atmosphere, and narrative through visual media

The portfolio needed to hold all three without forcing them into separate categories. The shell approach lets projects exist as part of a larger system rather than isolated case studies.

Small decisions that mattered

A few choices shaped the final feel:

• Keeping the visual language restrained so the work itself stays primary
• Using a dark, focused environment that feels more like a workspace than a brochure
• Letting the interface reveal itself gradually instead of explaining everything at once
• Treating the site as both a portfolio and a small piece of interactive design

None of these are revolutionary on their own. Together they create a consistent tone.

What’s next

This version is a starting point. I plan to expand the project documentation, add more process notes, and continue refining the shell itself. Portfolios should evolve the same way the work does through iteration, not sudden redesigns.

If you’re here looking at projects or considering collaboration, the work is the main thing. This post is just context for how it all came together.