I Built a Portfolio Website. Then I Realized a Portfolio Isn't Enough.

I was selling websites that help businesses get discovered through SEO and visibility.

Then I thought to myself:

Why am I not applying the same thinking to my own website?

A portfolio, at least in my mind, was supposed to be a display of the things I had created: projects, skills, experience, maybe an impressive collection of technologies I knew how to use.

So when I started rebuilding my portfolio website, I was genuinely excited.

I wanted it to look good. I wanted my projects to be presented properly. I wanted the site to feel like something I could finally be proud of.

And eventually, I put it online.

I expected to feel accomplished.

Instead, I felt a little empty.

Not because I disliked the website. I actually liked it.

The problem was that I started asking myself a different question:

What's the value of having a website that communicates almost the same thing as my GitHub, LinkedIn, or resume?

If someone wants to know what technologies I use, they can look at my GitHub.

If they want to see my education and experience, they can look at my resume or LinkedIn.

If my portfolio is simply another place where I list my projects and skills, then what exactly is it doing?

That question changed how I started thinking about my website.

A Portfolio Should Do More Than Display Your Work

I think I initially approached my portfolio like a gallery.

Here are my projects.

Here are my skills.

Here's my experience.

Here's how you can contact me.

Done.

But a website isn't valuable simply because information exists on it.

It needs to communicate something.

For a business, that might be trust.

It might be credibility.

It might be visibility in search.

It might be making it easier for a potential customer to understand what the business does and eventually become a customer.

That's the way I was already thinking about websites for businesses.

So I started asking myself:

Why shouldn't my portfolio do the same thing for me?

If I'm building websites that are supposed to communicate value, attract the right people and make it easier for them to take action, shouldn't my own website demonstrate that?

That became the point where my portfolio stopped feeling like a resume on the internet.

It became a project in itself.

My Website Became Part of the Proof

One thing I've started to appreciate is that when you're a developer, people aren't only looking at the projects you show them.

They're also looking at how you present those projects.

If I tell someone that I care about performance, my own website should be reasonably fast.

If I say I care about responsive design, my website should work properly on a phone.

If I talk about accessibility, I shouldn't treat it as something that only matters for client projects.

If I say I care about security, I should at least be thinking about security when I build my own applications.

And if I tell a business owner that their website should communicate their value clearly, mine should probably do the same.

The website itself becomes part of the portfolio.

That realization changed how I approached the project.

I became less interested in simply adding more things and more interested in asking whether each part of the website had a purpose.

I'm Still Figuring It Out

I don't think I've suddenly figured out the perfect formula for a developer website.

I'm still learning.

There are areas of development where I have more experience than others. There are things I would build differently today than I would have a year ago. And I'm deliberately spending more time learning about cybersecurity because I want security to become a bigger part of the kind of developer I become.

But I think that's okay.

A portfolio doesn't need to prove that you're the best developer in the world.

Especially when you're early in your career, that's impossible.

It should show where you are, what you've built, how you think, and where you're going.

And maybe that's what I was missing the first time around.

So What Is My Portfolio For?

My portfolio isn't meant to replace my GitHub.

It isn't meant to replace LinkedIn.

It isn't meant to replace my resume.

It has a different job.

It's the place where I can bring everything together and communicate the bigger picture.

What can I build?

How do I approach problems?

What do I care about?

What am I learning?

And, eventually, can I help you solve a problem?

That's the standard I'm trying to hold my website to now.

I started building a portfolio because I wanted somewhere to display my work.

I ended up realizing that the website itself is part of the work.

And if I'm going to build websites that help other people communicate their value, I think I should start by making sure mine communicates mine.