I got tired of my portfolio being a claim instead of proof. So I rebuilt it as a system that has to work — not a page that says it does.

HI WEBINATOR runs the full MERN stack (MongoDB, Express, React, Node), and I set one rule for myself going in: nothing gets featured unless it's actually live and the code is actually public.

Two projects inside it push in pretty different directions. Nuvara is the "make the data behave" problem — Redux Toolkit managing cart state, auth, and product filtering, where the challenge is mostly invisible plumbing that has to just work. RANDOOM is almost the opposite — a Web3 and visual identity piece where the problem is closer to brand and feel than logic.

Sandwiched between those are 7+ smaller builds — a furniture store, a food delivery flow, a handful of UI/UX conversions where I took static designs and turned them into working interfaces. Different clients, different constraints, different muscles each time.

The detail I care about most is small: the contact form runs on EmailJS and it actually sends. Not a mailto link, not a "coming soon." If it's on the site, it works — that was the whole point of building this instead of just writing a resume.

Honestly, the portfolio itself ended up being the hardest project on the portfolio. Scoping "how much is enough" for something that's never really finished was harder than any single feature inside it.

How do you know when a personal project is actually done — or do you just ship it before you talk yourself into one more feature?

Project :

Live portfolio: https://hiwebinator.com

Case study: https://www.behance.net/gallery/249494117/HI-WEBINATOR-Modern-MERN-Stack-Developer-Portfolio