Hey there! Iâm Ranjith Kumar, and Iâm super excited to take you along on the wild ride of building my first portfolio website. Picture this: a newbie coder, a bunch of YouTube tutorials, and a dream to create something awesome. Thatâs where it all began. In this post, Iâll walk you through how I designed, coded, and hosted my portfolioâand added some fancy extras like a 3D neural network animation. Grab a snack, settle in, and letâs get started!
1. The Spark: Why I Needed a Portfolio
So, why build a portfolio? Well, as a fresh grad eager to show off my skills, I figured a website was the perfect canvas. I wanted to prove I could code, design, and maybe even impress a future employer or two. Plus, Iâll admitâI was itching to play with some cool tech and see what I could pull off. Spoiler: it was tougher than I thought, but oh-so-rewarding.
2. Designing the UI: Figma to the Rescue
Iâm no design guru, so I turned to Figma after hearing itâs free and beginner-friendly. Armed with coffee and determination, I dove into YouTube tutorialsâshoutout to channels like DesignCourse and Flux Academy for saving my sanity. I spent hours experimenting with layouts, fonts, and colors. My first design? Letâs just say it looked like a rainbow threw up on my screen. But after tweaking (and maybe a little crying), I crafted a clean, modern UI that screamed âme.â I was proudâand honestly, a little surprised it didnât suck.
3. Coding the Vision: HTML, CSS, and a Dash of JS
With my Figma design ready, it was time to code. HTML and CSS are my comfort zoneâI structured the page to match my layout and styled it to perfection (or so I thought). JavaScript, though? Thatâs where the real adventure began. I wanted interactivityâsmooth scrolling, hover effects, the works. Hereâs a snippet of my nav bar CSS, because who doesnât love a sticky header?
.nav-bar {
position: sticky;
top: 0;
background-color: #333;
z-index: 100;
}
Getting it right wasnât easyâI spent an embarrassing amount of time wondering why my hover effects wouldnât work (spoiler: I forgot to add the JS file). But when it all clicked, I couldnât stop grinning. My static design was alive!
4. Going Live: Hosting on GitHub.io
Next step: getting my masterpiece online. GitHub.io was my pickâfree, simple, and tied to my GitHub repo. I created a new repository, pushed my files, and boomâmy portfolio was live at [yourname].github.io. The first time I loaded it in my browser, I felt like a rockstar. I may have refreshed the page 20 times just to make sure it wasnât a fluke. Hosting was the easy part; the real challenge was still ahead.
5. The Glow-Up: A 3D Neural Network Animation
After admiring my site for a bit, I realized it needed something⌠extra. It was cool, but not âwow, thatâs dopeâ cool. As an AI fan, I got this wild idea: what if I added a 3D neural network animation in the background? Picture neurons firing as you move your cursorâinteractive and nerdy, just my style. I had no clue where to start, so I teamed up with Claude AI. It pointed me to Three.js, and after hours of research (and a few âIâm in over my headâ moments), I built it. The network randomly lights up with cursor movement, and honestly, itâs hypnotic. My friends said itâs like my brain on caffeineâchaotic but beautiful.

6. Dark Mode: Because Night Owls Rule
Another must-have? Dark mode. Iâm a night owl, and staring at a bright screen at 2 a.m. is no picnic. Adding it was a puzzleâCSS variables for themes, JavaScript to toggle and save preferences. I wrestled with bugs (like forgetting to update all the colors), but eventually, it worked. Now, one click flips the site to dark mode, and it even remembers your choice. Itâs a small win that feels hugeâespecially when Iâm coding in the wee hours.
7. Building the Blog Homepage: From Chaos to Calm
While working on my portfolio, I decided I needed a blog tooâa place to share my journey. I scoured sites like Medium and WordPress for inspiration, sketching layouts like a mad scientist. My early designs were a messâtoo many buttons, clashing colors. But after several rounds of âthis isnât it,â I landed on the current homepage. Itâs simple, readable, and (dare I say) pretty slick. Iâm happy with it, but Iâm curiousâwhat do you think? Does it work for you, or should I tweak it more?
8. The Struggles: Tears, Code, and Coffee
Letâs talk struggles, because this wasnât a fairy tale. Making the site responsive was my Everestâmedia queries turned into a game of whack-a-mole. Fix the desktop view, break the mobile one. I spent hours tweaking pixel sizes, cursing my screen. Then there was the JavaScript for the neural network. As a JS rookie, I stared at error messages like they were alien hieroglyphs. One night, I had so many tabs openâStack Overflow, MDN, YouTubeâthat my laptop begged for mercy. But with grit and caffeine, I cracked it. Every bug fixed was a mini-party in my head.
9. How I Decided on the Final Version
Settling on the final design wasnât plannedâit evolved. After the animation and dark mode, I kept tweaking, asking myself, âDoes this feel like me?â I almost added a chatbot (overkill, I know), but decided simplicity was key. One day, I showed it to a friend who said, âDude, stop messing with itâitâs awesome.â Thatâs when I knew Iâd hit the sweet spot: functional, unique, and true to my vibe. Itâs not perfect, but itâs mine.
And thatâs the tale of my first portfolio! Itâs been a blastâfrustrating, thrilling, and totally worth it. If youâre thinking of building your own, do itâyouâll learn so much. Iâd love your thoughts: Do you like the design? The animation? Hit me up with feedback or just say hi:
Join the Discussion (0)
Comments via GitHub Discussions: This blog uses Giscus, which leverages GitHub Discussions for comments.
You'll need a GitHub account to comment. Comments will appear in a dedicated Discussion category within the blog's repository.