Aya

Building an Arch Linux Themed Portfolio: An Inspired Journey

I'll be honest, this portfolio wasn't meticulously planned out from day one. It was more of a creative experiment fueled by inspiration, nostalgia, and vibe coding.

What made this project different was having a complete vision from start to finish, something I'd never experienced before. That clarity changed everything. I have a few unfinished portfolios sitting in folders somewhere, projects that never got deployed, never saw the light of day.

But this time, knowing exactly where I wanted to go made all the difference. Having a vision isn't just important, it's everything.

The Inspiration

A few months ago, I stumbled upon an absolutely wild portfolio design at https://mitchivin.com/. I'm sure you've probably seen it before, the entire portfolio looked like the classic Windows XP interface. The taskbar, the window chrome, the iconic "My Computer" folder aesthetic.

Then there was another developer who went the hacker route with a Kali Linux terminal interface. Dark, minimal, and dripping with that cybersecurity edge.

I saw these and thought: Why not Arch?

As someone who's been using Arch Linux for a while now, there's something special about it. It's minimalist, it's powerful, and it has this clean aesthetic that I genuinely love. The Arch blue, the simplicity, the "you know what you're doing" vibe, it all clicked.

The Vision

I wanted to create a portfolio that:

▶Felt like a real terminal experience - but polished and professional

▶Told my story through interface design - the visual aesthetic would reinforce who I am in the data engineering space

▶Was functional AND beautiful - not sacrificing usability for looks

▶Matched my personality - minimalist, technical, and slightly unconventional

The Development Process

Here's where it gets interesting. This wasn't built with a Figma mockup and a detailed spec. It was organically developed.

What I mean is:

▶I'd sketch out a component, build it, and if it felt right, I'd keep it

▶I'd adjust colors until they resonated with the Arch aesthetic

▶I'd try different terminal commands for titles ($ cat profile.txt, $ ls -la) and keep what sounded natural

▶I'd build features organically, what would be cool here?

The landing page animation with morphing characters? That came from wondering how can I make this feel alive? Shell cards with borders and hover effects? Just playing around until it looked crisp.

The Technical Foundation

Of course, beneath the creative process was solid tech:

▶Next.js 16 with TypeScript for the framework

▶Tailwind CSS for styling (with heavy customization for that Arch color palette)

▶React components built with a terminal aesthetic in mind

▶MDX for blog content (like this very post)

▶SVG icons instead of emojis for that professional, interface-driven look

The Color Palette

The Process: Iterative and Flexible

What made this approach work:

●Start with the shell aesthetic - build the core look and feel

●Add components incrementally - navbar, taskbar, panels, cards

●Populate with real content - integrate actual projects, blog posts, skills

●Refine and iterate - adjust spacing, colors, interactions based on feel

●Polish and ship - minimize, optimize, and deploy

No analysis paralysis. No overthinking. Just building, feeling, and adjusting.

What I Learned

This organic approach works when:

▶You have a clear aesthetic direction (Arch Linux aesthetic, in this case)

▶You understand your audience

▶You're willing to iterate and refine

▶You don't get too attached to early decisions

This approach struggles when:

▶You lose sight of functionality

▶You prioritize style so much that UX suffers

▶You're building for a mainstream audience expecting conventional design

The Result

A portfolio that:

▶Feels like stepping into my terminal

▶Showcases my projects and expertise

▶Tells a story through its design

▶Is genuinely mine—not a template, not generic, just... me

Your portfolio doesn't need to be a design masterpiece. It needs to be you. And honestly? The experimental, slightly unconventional approach often lands better than something sterile and over-designed.

---

TL;DR: I saw cool retro OS portfolios, thought "why not Arch?", built it, and somehow ended up with something I'm genuinely proud of. Sometimes the best ideas come from inspiration + experimentation + not overthinking it.