Case study
SiteForge
A command-line tool for building interactive sites rather than static ones. It handles video backgrounds, section structure, effects, and ships with a demo recorder and an audit step — so you can produce something, capture it, and check it before publishing. TypeScript throughout.
What it does
Video backgrounds, section scaffolding, effects, then a demo recorder to capture the result and an audit pass before you ship. The point is a single tool covering the whole path from empty directory to something you can look at and verify.
Where it came from
This grew out of an earlier bash script that did one narrow thing — turning a video into a scroll-driven site. That version still exists as video-to-site and is listed separately. SiteForge is the same idea generalised: a real CLI in TypeScript instead of a pipeline, covering more than just video.
How it is built
TypeScript for the CLI and the scaffolding, with shell for the parts that shell is genuinely better at. Roughly 95% TypeScript in the repository.
Why the recorder and audit exist
Interactive work is hard to verify by reading it. You cannot tell from the source whether a scroll animation actually lands or whether a section fights the one above it. Recording it and looking is the only honest check, which is why those are part of the tool rather than something you do afterwards by hand.
What I learned
- Being able to see the result is the difference between iterating and guessing.
- A narrow script is a good way to find the real problem; the general tool comes after, not before.
What it doesn't do yet
Listed deliberately — a project's limits are as useful to a reviewer as its features.
- Actively changing.
- No public demo — repo only.