Why I Created My Portfolio Website Before the Projects

After nearly a month of battling analysis paralysis around design, I can finally call my portfolio page done, or at least done enough.

My biggest takeaway? I struggle with making design decisions. Choosing color combinations, button styles, and font sizes for headers versus paragraphs was harder than I expected. I don’t think I have the “design eye” just yet, but I know it’s something I can develop over time.

Yes, I know the contact section appears both on the homepage and on a separate page. My reasoning was simple: if someone wants to reach out without scrolling all the way down, they should be able to. I just want to make it as easy as possible for potential clients to contact me.

I used custom post types for both the Projects and Articles sections, even though I could’ve just used the default Posts. I chose to do it this way to build muscle memory with CPTs and keep practicing more advanced WordPress development techniques.

I also created my own custom WordPress theme from scratch, instead of using pre-made templates or page builders. It was my way of getting more hands-on with WordPress development and having full control over the site’s structure and styling. For the CSS, I used Tailwind v4.1, which helped speed things up without sacrificing customization.

Now, you might be wondering why I made a portfolio website when I don’t have any projects to showcase yet. It might be unconventional, but I just wanted a web space I could truly call my own. That’s also why I bought my domain early on. There’s something fulfilling about seeing a real website online that has your name on it and reflects the work you’ve put in. I’d even consider this portfolio a project in itself.

If you’re curious about how the site was built, the theme’s source code is available on GitHub.

Hopefully, I’ll be able to fill out the Projects section over time to showcase my growth and the things I’ve built. For now, this is where it starts.