CSS Cascade
A personal project to understand and explain how the CSS cascade resolves competing declarations.
View Project : CSS Cascade

In 2019, I was studying chartered accountancy when I watched my cousin design and build a website from scratch, writing code and seeing it take shape in real time. I knew I'd found the work I wanted to do. So I learned to build for the web.
Since May 2020, I've designed and built websites for clients from the ground up, handling everything from prototyping in the browser to deployment. I write semantic HTML and resilient CSS that communicates the design intent to the browser, leaning on the cascade and intrinsic layouts instead of hardcoded breakpoints or magic numbers. The interface leverages the web platform (HTML, CSS, and JavaScript), with a framework on top only where it earns its place.
I build this way because it lasts, and because it includes more people. The platform outlasts every framework, so the HTML and CSS stay portable across frameworks and a change of stack doesn't mean a rewrite. What I ship stays accessible regardless of ability, device, browser, or connection speed.
Performance is part of that, not a separate pass: I keep the payload small, and I treat a slow connection as a condition to support rather than an edge case to apologise for.
I like working alongside developers and teams who see frontend the same way: a foundation worth building well, not a layer to rush past. I'm looking for a full-time role, based in Mumbai but open to relocation and to remote work.
A selection of websites I designed and built. Each one shaped by its purpose and the people it serves.
If you're hiring, have a question, or just want to say hello, I'd like to hear from you.
hello@arpit.codes