Where it started
We wanted to know what is left when every aid is taken away: no framework, no page builder, no content system. Only HTML, CSS and JavaScript, written by hand.
What we assumed
If we can build a page that moves tens of thousands of points on the graphics card and still runs under the strictest security rule a browser knows, the rest is craft.
What did not work
Our first smooth scroll ran into an endless loop. Browsers round the scroll position to whole device pixels, and at fractions the stop condition was never met: the page scrolled itself along on every frame and cancelled every jump command from outside.
The only clue was a symptom that looked like a browser bug. The rule since then: any approach to a rounded value needs a catch threshold of at least one unit.
What we built
A single point object on the graphics card whose shapes are sampled from a helper canvas. No 3D model, no asset file.
Four device classes derived from three signals, so the page runs on weak hardware instead of stuttering.
Served under the rule default-src none: the page is not allowed to load anything on its own.
Result
The page is served statically, with no server process that could fall over at night.
The technique behind it now sits in our start page too: the point build at the top works the same way, only smaller and without an outside library.
Something similar in mind? We tell you up front what we think is doable and what is not.
Start a project