Use case
Ramp a teammate with one readable page
Systems, decisions, and “where it usually breaks” as a briefing they can reopen. Hand them a URL instead of a hallway recap.
Why a zine for this
- A durable briefing they can read on day one and reopen in week three.
- You control the audience: new engineer, PM, or contractor.
- Regenerate the same link when the system or decision changes.
Example zines
Each card opens a full hosted page — structure and tone tuned to the topic.
How it works
- Name the system or decisionWhat they need to know, what to skip, and who they are. Optional: the usual failure modes.
- Generate a pageWe turn the brief into one hosted HTML briefing with sections and callouts.
- Share the URLDrop it in onboarding or Slack. Update the brief and regenerate when the ground truth moves.
Starter brief
A one-pager on our checkout flow: what it does, the moving parts, and where it usually breaks.
Audience: A new engineer in week one.
Questions
- What do I get?
- One hosted HTML page at a shareable URL. It is a briefing to read, not a chat to continue.
- Is this internal-only?
- Each zine is a public URL. Do not put secrets in the brief. Write the kind of context you would put in a wiki.
- How do I start?
- Register for the beta. After approval, describe the system or decision on the new-zine form. When generation finishes, the page appears in My zines.
- Can I revise it after a launch?
- Yes. Edit the brief and regenerate. The public URL stays the same.
Create a briefing
Sign up for the beta to request access. Once approved, describe the system or decision in a short brief and we will generate a hosted page you can hand to a teammate.