As you may have noticed, my portfolio is not open-source. While I’m a strong advocate for open-source software, this project is an exception. In this post, I’ll explain why I’ve chosen to keep this site closed-source and the principles behind that decision.
My Stance on Open Source
I firmly believe in the power of open-source software. It fosters collaboration, innovation, and transparency. I actively use and contribute to open-source tools, and I encourage others to do the same. However, when it comes to personal portfolios, I’ve decided to take a different approach.
The Problem with Open-Source Portfolios
Avoiding Plagiarism
One of the main reasons I’ve kept this site closed-source is to prevent plagiarism. A portfolio is a reflection of your skills, creativity, and personality. It should be a unique creation that showcases what you’re capable of.
When a portfolio is open-source, it becomes easy for others to copy the code, change a few details, and pass it off as their own. While some might argue that imitation is the sincerest form of flattery, I believe it undermines the effort and originality that goes into building something from scratch.
The Brittany Chiang Example
A great example of this is Brittany Chiang’s portfolio. Her site is beautifully designed and open-source, which has led to countless developers copying it verbatim. While I admire her decision to open-source her work, I’ve seen too many instances where people simply replace her name with theirs and claim it as their own. This isn’t just lazy—it’s dishonest.
Why This Site Isn’t Open Source
Designed as a Template
This site was built as a Nextjs template, making it incredibly easy for someone to clone, modify, and repurpose. Even someone with minimal programming knowledge could replace the text and images and call it their own. While I believe templates are a great way to simplify website creation, I don’t want my portfolio to become a free-for-all.
Minimalistic Design
From a design perspective, this site is intentionally simple. It’s built with plain HTML and CSS, with no JavaScript. Anyone with basic web development skills could recreate it. However, the simplicity is deliberate—it reflects my preference for clean, functional design.
What sets this site apart is the content management system. Posts are created by adding a single file, and the site dynamically generates the rest. This makes it easy for me to update and maintain, but it’s not something I want to hand over for others to replicate without effort.
Inspiration vs. Plagiarism
The line between inspiration and plagiarism can be blurry. While it’s perfectly fine to draw inspiration from others’ work, directly copying someone’s portfolio crosses that line. A portfolio should be a personal project that demonstrates your abilities, not a carbon copy of someone else’s hard work.
Ultimately, where that line is drawn is subjective. Everyone has their own opinion, and I respect that. For me, keeping this site closed-source is a way to protect my work while encouraging others to create something uniquely theirs.
Final Thoughts
While I’m a strong supporter of open-source software, my portfolio is a personal project that I’ve chosen to keep closed-source. It’s a reflection of my skills, creativity, and values, and I want it to remain uniquely mine.
If you’re building your own portfolio, I encourage you to take the time to create something original. It’s not just about the code—it’s about showcasing who you are and what you can do.