Catalog
Name every screen, who can use it, and which git paths belong to the how-to.
A Devrecated Solutions product
Up-to-datehow-tosfortheportalyourteamalreadyuses.
Portals grow. People forget. DocPuppet recaptures the screens that matter, writes how-tos, and appends What’s new with demos so employees and clients can see what shipped and how to use it.
Capabilities
One catalog. Capture, how-tos, and What’s new.
The plan, stills, clips, and intended-behavior verdict live in one engine. The handbook you host is the proof. DocPuppet does not send mail.
Capture
Playwright stills and per-page clips against the live origin, including an auth prelude.
How-tos
Purpose, where to open it, and look-outs. Recapture keeps the human copy.
What's new
Dated sections append. Commit subjects come from the app repository.
Scope
When paths are set, recapture only the pages whose source actually changed.
Verdict
Pass, fail, or uncertain from what the running app showed versus the needle you named.
How it runs
A CLI against any http(s) origin
Point a spec at a running app. Autodevelop subscribers receive DocPuppet. The CLI also runs on its own.
01
Point at a running origin
A catalog JSON is enough. DocPuppet does not need Autodevelop login, tickets, or mail.
02
Capture the screens people forget
Sign-in, dashboards, boards, and the rest of a large portal. Session survives across pages.
03
Ship the handbook
How-tos and What’s new land in the docs tree you already host. Employees and clients open that URL.
doc-puppet capture --origin https://your-portal.example --spec catalog.json --site --videoExample
See a captured handbook
The public example is a dealer portal handbook: how-tos, stills, clips, and What’s new. The product is the engine and this site, not that one app.