The workflow, in plain English
Before: You’re reading API docs. There’s a code example. “Would this work for my case?” You open CodeSandbox, paste, modify, run, compare with docs. 5 minutes per example.
After: Below each code example in the docs, a “Run” button appears. Click it. The output renders right there. Edit the code inline. Change a parameter and run again. The documentation became a playground. You test ideas at the speed of reading.
Why traditional tools can’t: Interactive docs require the site author to build playgrounds. Dassi adds them to ANY documentation page, even ones with static code blocks.
Step-by-step
- Open the documentation page with code examples.
- Ask dassi to turn a specific snippet into an interactive playground.
- Run, modify inputs, and re-run to validate behavior.
- Copy the working snippet into your codebase.
Example prompts to try
- “Make this code sample runnable and show output below.”
- “Change the example to match my API key and endpoint.”
- “Add a test case for error handling.”
Tips for better results
- Be specific about what you want injected into the page (buttons, filters, a panel, a summary, etc.).
- If the page has multiple sections, tell dassi exactly what to focus on (e.g., “the transactions table” or “the diff for file X”).
- Prefer safe workflows first: draft, summarize, label, and prepare — then take actions (submit, purchase) only after review.