Journal
Notes from
the build.
An open record of systems, experiments, and engineering decisions. What exists, how it works, and what is still being figured out.
Explore the notebookColor is more than RGB
Why a useful color engine must reason about perceptual spaces, gamut, hue paths and contrast—not just hexadecimal values.
Read the storyThinking
out loud.
Systems, experiments and decisions.
A record of the work as it evolves.
- Engineering Notes
Geometry before the editor
Inside the geometry kernel: source-native Bézier curves, derivatives, measurable paths and numerical precision before any editor UI.
- System Notes
Motion as data
Separating an animation description from timing, browser playback and generated CSS makes motion reproducible and reusable.
- Core Notes
Building an interaction core
Why input recognition and motion physics belong in a reusable library, not inside each individual interface.
- Build Log
Raster processing without changing the original
A processing pipeline built around inspection, explicit transformations, output validation and the untouched source.
- System Notes
An interface core without a UI kit
Shared tokens and validation rules can travel between projects without forcing every project to look the same.
From the archive
EARLIER THOUGHTS / SAME CURIOSITY- Art direction
The website should follow the project
Why the useful starting point is the project itself—not a page layout, theme, or visual trend.
- Digital design
Mobile is a composition, not a smaller desktop
Responsive work becomes stronger when the same content is deliberately re-composed for a different screen.
- Creative process
A custom website still needs a system
Original pages are easier to evolve when the underlying content, motion, and visual rules are deliberately separated.