Small browser experiments have an awkward habit of becoming infrastructure projects. A few lines of HTML, CSS, and JavaScript turn into a repository, a build, a deployment, and a link that asks the reader to leave the article at exactly the moment the idea should become tangible.
The better shape is smaller: explain the idea, let it run, then keep reading.
This example is not a video or a screenshot. The button is real. It is a plain browser document published as an immutable Bookshelf revision and placed inside this article with a narrow integration contract: one public URL.
Why pin the revision?
An article is a record of what the author meant at publication time. If an embedded example can silently change later, the surrounding explanation can become wrong without the article itself changing. A revision-specific URL keeps the two in lockstep.
<iframe
src="https://embed.56clindsey.com/p/PROJECT_ID/REVISION_ID"
sandbox="allow-scripts"
title="A runnable example"
></iframe>The blog does not know how Bookshelf stores projects, who authored them, or how their code is rendered. Bookshelf owns those concerns. The article owns the story and the space the example occupies.
The useful constraint
The first version supports vanilla HTML, CSS, and JavaScript. That is deliberately less powerful than a general application environment, but it is enough for diagrams, UI ideas, animation studies, API explanations, and the small moments where seeing a concept move matters more than installing a framework.
There is plenty to add later. For now, the important thing is that a small idea can stay small—and still have a place to run.