Numbers you can trace
Every figure on the site comes from a README, a live product or a shipped UI. Where a number doesn't exist, the site says nothing rather than rounding up.
600Interface
VED.EXE
This site. You are reading one of the things it describes.
- Role
- Designer and developer.
- Year
- 2026
- Status
- Live. You're on it.
- Stack
- Next.js 16, React 19, TypeScript, Tailwind CSS 4, View Transitions API, GitHub GraphQL
- animation libraries
- 0
- reaches every page
- ⌘K
(57) Abstract
A portfolio set as a patent filing. Each project is a sheet with figures and numbered claims, and the claims say exactly what the engineering does.
Background
The previous version was a retro arcade: CRT scanlines, a boot sequence, neon. It was fun and it hid the work. This version puts the work first and lets the jokes live in the margins.
Drawings
- FIG. 1Anatomy of a sheet: header strip, gutter with line numbers, figure with reference numerals, claims.
Detailed description
Server first
Pages are React Server Components. Client code is limited to the command palette, the figure on the cover, the sheet counter and a copy button.
Motion as material
Figures draw their lines once as they enter and then hold still. Project plates morph into case studies with the View Transitions API. With reduced motion, everything is simply there.
Keyboard complete
⌘K or / opens a command palette that reaches every page, link and setting. It opens instantly because you might use it a hundred times.
Live build activity
Contribution data comes from the GitHub GraphQL API with hourly regeneration. Without a token the section degrades to what the public API can say.
What is claimed is:
- 1.
A portfolio in which every number is traceable to a repository or a live product.
- 2.
The portfolio of claim 1, wherein every page can be reached from the keyboard.
- 3.
The portfolio of claim 1, wherein no testimonial was invented.