I Turned My Worst Portfolio Into a Production-Level Developer Website Using GitHub Copilot

Priyanshu Bisht — Thu, 04 Jun 2026 07:35:12 +0000

This is a submission for the GitHub Finish-Up-A-Thon Challenge
What I Built

I rebuilt and completely redesigned my personal portfolio website — a project I originally started back in January 2026 when I was still learning the basics of HTML, CSS and JAVA Script.

At that time, I didn’t really understand how to create a portfolio that actually represented me as a developer. I just wanted to build something from scratch and put myself online.

The result was… honestly terrible 😅

During the GitHub Copilot Finish-up-athon, I decided to revive an abandoned project and turn it into something I could genuinely be proud of.

This project means a lot to me because a portfolio is more than just a website — it represents your identity as a developer. It’s often the first thing recruiters, teams, and collaborators see.

Rebuilding it honestly felt like rebuilding my confidence as a developer too.

Demo

After

Live Project

The Comeback Story

This portfolio started as one of those unfinished beginner projects sitting quietly inside my GitHub repositories for months.

I originally built it when I had very limited frontend experience. The design was basic, the structure was weak, and eventually I stopped working on it because I didn’t know how to improve it further.

The GitHub Copilot Finish-up-athon gave me the perfect reason to return and finally finish what I had abandoned.

Instead of starting a brand-new project, I wanted to revisit something old and prove to myself how much I had improved.

During the challenge, I:

redesigned the entire UI/UX
rebuilt multiple sections from scratch
improved responsiveness across devices
refined typography, spacing, and layout balance
added real project showcases
created more cinematic frontend interactions
redesigned the navigation and hero sections

One of the biggest lessons during this process was learning how to iterate properly. At first, many outputs were nowhere close to what I imagined. Some layouts felt generic, some sections looked AI-generated, and many interactions lacked personality.

So instead of settling for average results, I kept refining prompts, restructuring ideas, testing layouts, and improving the direction step-by-step until the website finally felt personal.

That process taught me something important: good design rarely happens in one attempt. It’s built through iteration.

My Experience with GitHub Copilot

GitHub Copilot genuinely helped me move faster throughout the rebuild process. What I liked most was the ability to experiment with different ideas quickly without losing momentum.

I also combined GitHub Copilot with prompt-engineering workflows to improve output quality and better communicate the design direction I wanted.

The biggest advantage wasn’t just code generation — it was momentum.And honestly, that’s what made this challenge meaningful for me.

Not just starting something —
but finally finishing it.

DEV Community: Priyanshu Bisht

I Turned My Worst Portfolio Into a Production-Level Developer Website Using GitHub Copilot