Skip to main content
Okhare Paul — Portfolio©2026
000
Back

Case study · 05 / 12

Pod Website

A launch site that ships five dependencies

Year
2026
Focus
Next.js
Status
In development
Coming soon: Pod Website is not public yet
Fig. 05 — Pod WebsiteFive dependencies, every page built ahead of time.
About the project

The website that will launch the Pod app: a fully static Next.js site in strict TypeScript, with hand-written canvas graphics and only five runtime dependencies.

A launch site has one job: load at once and feel like the product. I kept this one deliberately small. Every page is built ahead of time, so the server has nothing to work out when a visitor arrives. The pages are data: each is a typed record, and one renderer turns a record into sections, which means a new page is content, not code. The motion is real, with smooth scrolling, page transitions and a field of dots drawn on a canvas, but it is written by hand in place of heavy libraries, and it steps aside for anyone who asks for less motion.

Main features

What it does

  1. 01Prebuilds every page, so there is nothing to render on request
  2. 02Builds pages from typed content records through one block renderer
  3. 03Slides between pages with the browser's own View Transitions
  4. 04Draws its dot field on a 2D canvas, with no WebGL
  5. 05Shows the app's screens inside the page without their styles leaking out
  6. 06Sends strict security headers on every response
Approach

How it was solved

  1. 01Used static generation with unknown addresses refused outright, so the site is as fast as a file and has no server logic to attack
  2. 02Kept the client small: 13 components render on the server and only 12 ship JavaScript
  3. 03Self-hosted the fonts, so text paints without a request to a third party
  4. 04Decided the loader's state in a script that runs before first paint, so the first frame is never wrong
  5. 05Capped canvas resolution, stopped drawing off screen and in hidden tabs, and held physics to a fixed step
  6. 06Drove smooth scrolling and scroll-linked animation from one clock, so they cannot fall out of step
  7. 07Locked the Content Security Policy to the site's own origin, with HSTS and frame protection
  8. 08Mounted the app-screen mock-ups in a shadow root, so two design systems share a page without colliding
  9. 09Synced design values by reading the design file as a syntax tree with an allow-list, never by running it
  10. 10Tested the production build, not the dev server, so the security headers are part of every run
Results

Five runtime dependencies in total. 32 end-to-end tests on desktop and phone, and 85 unit tests, all run against the production build.

Technologies

Stack

Languages
TypeScript (strict)CSSHTML
Front-end
Next.js 16 (App Router)React 19React Server ComponentsView Transitions API
Motion and graphics
GSAPScrollTriggerLenisCanvas 2D
Performance
Static generationnext/fontnext/image (AVIF, WebP)
Security
Content Security PolicyHSTSPermissions-Policy
Testing and tools
VitestPlaywrightESLintsharpacorn

Not public yet. The link goes here the day it launches.

Coming soon: Pod Website is not public yetMeet the developer
Next project · 06 / 12Gilmore