tl;dr: one idea per site, plan it in screens of scroll, one gsap timeline tied to the scroll, turn every rule into a browser check, then polish on a real phone. kelvin came first and set the template; sum, meridian and datum were built end to end by claude code on top of it. those three are free and open source (links at the end).
the four
kelvin: a portrait studio. scrolling turns a white-balance dial, from 3200k tungsten to blue hour
sum: a shop for one watch. it comes apart into its 147 parts, each one counted, and goes back together
datum: an architecture practice. a drawing is drawn and becomes the house standing on it
meridian: delivery tracking software. one zoom from the whole earth down to a single door
how they started (my actual prompts)
kelvin:
> an agency-grade site for a photography studio. layered and masked images, a model whose look changes as you scroll, a cinematic entrance, images that assemble themselves
claude code turned that into one idea: scrolling turns a white-balance dial, from warm tungsten to blue hour.
sum:
> cinematic explosion and view, something like 3d with explosion, then slow down, zoom in, pans, individual component etc. nice and crispy, with rotations if possible. work on phones even if a bit different
how kelvin was made (the template for the rest)
images (fal.ai, ~$6): one base portrait from gpt image 2.6, then three relit copies with its edit mode ("relight this exact photograph, keep every edge in the same position, change only the light"). no relighting in code: four photos that line up to the pixel, and scroll blends between them. birefnet cut-outs give a matte of the model (so the type sits behind her) and a kit flat lay that splits into 13 pieces that assemble.
gsap: no scrolltrigger. a small "director" reads the scroll each frame and drives paused timelines, pins are plain position: sticky, and everything is timed in screens of scroll so it plays the same both ways. one webgl2 canvas does the transitions between lights.
controls: arrow buttons and keys as well as scroll. tap to jump to the next scene, hold to play.
checks: puppeteer checks every scene on desktop and phone, in chrome and safari's engine. then a real iphone caught what the checks didn't: a gsap quickSetter on scale threw every frame on its older engine and killed the last scene.
sum, meridian and datum reused all of it: one idea, a score in screens of scroll, their own copy of the director and their own browser check. sum draws the watch in webgl2 from photos of its parts, meridian draws its map in canvas from real map data, and datum measures its drawing from its own photograph.
what went wrong (the useful part)
datum is a drawing that becomes a building, and for the whole first build no line was ever actually drawn: each one just appeared. every still looked right and every check passed, because "nothing half drawn at a pause" is true of a line that's never half drawn. we found it by breaking the page on purpose and seeing the check didn't care. lesson: a check means nothing until you've seen it fail.
to make one yours, paste this into claude code:
I'm adapting the [Sum / Meridian / Datum] GSAP site in [folder] to [my product / my data / my building].
Change only: [what]. Keep the score's shape, the scroll director, the step buttons and
arrow keys, and the rule that words and picture never share room.
Every word and number goes in content.ts. Anything measured from a picture is measured
by the scripts, never typed in.
After each change, build for production and run the site's check on a wide window and
a phone shape. Show me full-size frames of every rest before you call it done.
sites: https://www.aimdropin.com/gallery/gsap
code: https://github.com/akellaluvlace/aimdropin