What is Fixtureframe?
A release-content orchestration layer — approved product flows become help articles, screenshots, demos and videos, and refresh when the product changes.
Fixtureframe turns approved product flows into governed help articles, screenshots, guided interactive demos and walkthrough videos — then refreshes them when the product changes.
The working principle is one sentence, and everything else follows from it:
AI proposes, the deterministic runner executes, and a human approves.
Fixtureframe never silently publishes customer-facing content. A run produces a draft; a person approves it; only then does anything reach a destination.
Why the loop matters
Most documentation rots because the product moves and the screenshots do not. The usual fix is discipline — someone remembers to re-capture. Fixtureframe's fix is that a flow is a recorded, replayable artefact: when the release lands, the same flow runs again against the new build, and the diff is what a reviewer approves.
That is the difference between a content tool and a content pipeline. The mapping from published page back to the flow that produced it is what lets a re-run say "three screenshots on this page changed, here is the diff, approve?"
The shape of the work
Install the CLI
One command, no Node required.
Build a flow with your coding agent
From Studio sign-in and app context to a checked, replayed and published walkthrough.
Record your first flow
Capture yourself using the app and save it as a replayable flow.
Import what you already have
A deck, a PDF, a Google Slides link, or the pictures and clips on your disk.
Flows and runs
What gets stored, what gets executed, and what a run produces.
Flow files
The JSON is the authoring format: local pictures, narration and card text.
Outputs
Screenshots, GIFs, interactive demos, HTML demos and narrated video.