Skip to content
Takshak Mudgal

Colophon

How this site is made, and where its numbers come from. I built it as a small design system called Floorplan: the work is drawn the way a chip is laid out, in blocks, with every line meeting at a right angle.

The chip

Figure 1 on the home page is a silicon die in a ceramic package, drawn in code. A background worker paints the die when the figure comes into view: a seal ring, bond pads, I/O cells, a power ring, and one block per area of my work, filled with standard cell rows, memory arrays, a datapath or an inductor depending on the block. three.js turns that drawing into a material with thin-film iridescence, the effect that makes real dies shimmer under a microscope, and bonds each pad to the package with a gold wire.

The die carries two small marks a chip designer would recognise. Ⓜ 2026 is the mask work notice, the copyright symbol for chip layouts, and one corner holds a tiny lunar module, a nod to the Apollo Guidance Computer. Select a block and it lifts out of the die while the camera moves in, and the work behind that area is listed beside it. Without WebGL you see a still render of the same scene and the area panels still open; without JavaScript, the work each block stands for is linked further down the page.

Type

Headings and text are set in Archivo by Omnibus-Type, under the SIL Open Font License. It is a variable font with a width axis, so one family covers body text at its normal width and headings stretched to 116%, the way equipment nameplates are. Code is set in JetBrains Mono, also under the SIL OFL, because it is the face in my terminal.

Colour

Neutrals sit slightly towards blue, like a wafer. Each area of work has one colour, used for the chip's blocks, the timeline and the small squares beside labels. I ran the five hues through a colour-vision validator: neighbouring hues stay distinct for normal vision, and colour never carries meaning without a text label next to it.

Neutrals, light and dark
paperPage
inkText and rules that matter
ink-2Body copy
ink-3Captions and labels
lineHairlines
Areas of work, light and dark
Product engineering
Terminal tools
Solana programs
EVM contracts
Open source

Where the numbers come from

Every figure was checked on 16 Oct 2026, and each case study lists its sources. Pull requests, commits and contributions come from GitHub's API, which also sees the private repositories I work in. Test counts and contract sizes come from the repositories themselves. On-chain figures come from read-only calls to Arc and Robinhood Chain. Anything I could not check is not on the site.

Stack

Framework
Next.js 16.4 with the App Router; every page is prerendered
UI
React 19.3, TypeScript 5.9, Tailwind CSS 4.3
3D
three.js 0.186, loaded only after the page is idle
Hosting
Vercel
Tracking
None. No analytics and no cookies; the theme choice is kept in your browser's local storage
Build
528b7f9

Questions about any of it are welcome at takshakmudgal@gmail.com. The résumé is the same content on one page.