Everyone has a portfolio. Very few have a paper trail.
ashokkumarpandey.com — portfolio site, delivered design through DNS
authorashok.com — Supabase Auth, PostgreSQL CMS, live publishing workflow
Finance Advisor — Gemini-backed advisory insight, Clerk multi-user auth
Sports Score Dashboard — five sports, live scores, one responsive interface
A portfolio site is usually a highlight reel: four screenshots, a gradient, a contact form. It shows you the finished surface of the work and none of the working. Which is fine, until the person reading it wants to know whether you can actually do the thing, and there is nothing on the page to answer that with.
This site is built the other way round. It is a folder — a researcher’s desk rather than a gallery wall. Roles, projects, client sites and coursework are filed as cases, each with the paper document on top and the loose notes, sketches and links scattered around it. You open a folder, pull out a file, and read the working.
The reason for the format is that my work has not been linear. A computer science degree at SRM has run alongside a business intelligence consulting role at ICON Resources, a web and CRM development internship at Rasalsi, freelance delivery of two live production domains for an author, four batches of Python and AI teaching, and a set of products built because the problems were interesting. Presented as a timeline, that reads as noise. Presented as an archive, it reads as what it is: a lot of different rooms, entered on purpose.
The through-line is a preference for finishing things. A Chrome extension published to the store rather than demoed. Two client domains pointed at real DNS rather than parked on a preview URL. An AI finance tool walked through with actual users rather than screenshotted with seed data. A teaching batch measured by whether every student could build and present their own project, rather than by attendance.
That preference has a cost, and it shows up in the stack. Shipping means learning the parts nobody writes blog posts about: Cloudflare records, ETL failure modes, Chrome offscreen documents, Zoho pipeline configuration, and the time management required to keep a 9.2 while doing all of it. None of it is glamorous. All of it is the difference between a project and a product.
The design of this site is a direct tribute to Mosby’s Files by Tubik Studio — an archive of American Modernist architecture built around the same folder metaphor. I rebuilt the structure because it solves a real problem: it lets a body of work be browsed the way it was actually accumulated, in layers, rather than flattened into a grid. The architecture is theirs. Everything inside the folders is mine.
The folder’s open. Start anywhere.