Method: learn by doing in a live sandbox. The blog's FAQ describes interactive docs that let readers "test, explore, and interact with the product directly inside the documentation." A sandbox goes one step further: readers edit real content, see the result instantly, and get automatic feedback on each task.
Try it: build an interactive topic
Edit the HTML on the left โ the preview on the right updates as you type. Complete the five tasks; each one ticks itself off automatically when your code is right. Stuck? Use Hint or Show me.
HTML
๐
All five tasks done! You just turned a flat page into an interactive topic โ headings for scanning, a collapsible tip, a table, a warning, and a cross-reference.Your code is saved in your browser, so you can come back later. The same HTML works in the ClickHelp topic editor's source view.
Why sandboxes work
- Readers learn by changing something and seeing what happens.
- Automatic checks give instant, specific feedback โ no waiting for a reviewer.
- Hints and "show me" keep people moving instead of giving up.
Related: Interactive API docs ยท Walkthrough