Why I Built My Portfolio
I mass-produce repos like a GitHub factory. They needed a home outside the pinned-repo grid. dbterm for databases, ProtoPeek for APIs, Quillpane for Markdown, Visualise OKLCH for colors. Plus the notes and opinions that come with building them. https://shreyam1008.com.np/projects/
How I Built My Portfolio
React, TypeScript, Vite, Tailwind, and Bun. Cloudflare Pages and Workers handle the hosting side. I ship the frontend, backend, and the strong opinions holding them together. The code, including the bits I'd probably rewrite tomorrow: https://github.com/shreyam1008/buggy
Challenges in Creating My Portfolio
The 2px alignment shift nobody notices. Except me. Now I can't unsee it. Also fitting projects, writing, and working tools into one site without making visitors need a map. Looking simple takes a suspicious amount of work.
How I Overcame Those Challenges
Break it. Fix it. Ship it. Repeat. I keep fussing over the small UI details, give the projects clear places to live, and automate the boring checks. Routes, links, builds. If it can be checked by a machine, I'd rather not remember it manually.
Inspiration
Open-source tools and homelab life. I'm the person who will spend twice as long self-hosting a NAS as it would take to pay for cloud storage. The principle. The uptime dashboard. The blinking LEDs. That same itch follows me into the things I build.
Lessons
The best UI is the one where nothing feels wrong and you can't explain why. That's the bar I keep chasing. The less glamorous lesson: a nice homepage still needs working links and docs people can actually use. The commit history continues.
Future Plans for My Portfolio
Keep building. Give dbterm, ProtoPeek, Quillpane, and Visualise OKLCH better guides and proper demos. Write down the useful bits before I forget them. Occasionally stop starting another repo. No promises. https://shreyam1008.com.np/log/
