Automatic Screenshot Citations
Insert real screen captures into articles, with a source citation
Showing the real screen makes an article more convincing
For articles about how to use a tool or introducing a service, an actual screenshot conveys more than text alone. Sorabun can capture a screenshot of the relevant page and insert it into the article to match the content.
Settings
Enable this under "Settings > Screenshot Citations (optional)".
| Item | Setting key | Description |
|---|---|---|
| Auto-capture | screenshot_enabled | Whether to insert screenshots into articles |
| Maximum count | screenshot_max | How many screenshots to capture per article |
| Capture service | screenshot_provider | ScreenshotOne or ApiFlash |
| API key | screenshot_api_key | The key for the service you chose |
| Capture width | screenshot_device | Desktop (1280x800) or phone (390x844) |
| Shot slots for steps | shot_slots | Leave a "capture this screen" slot in step-by-step sections (on by default) |
Match the capture width to the device your readers will be using. If an article explains a phone workflow but shows desktop screens, readers cannot compare them against what is in front of them.
Screens behind a login get a slot instead
Sorabun cannot open your admin panel or an app, so it cannot capture those screens. With shot slots (shot_slots) on, a step-by-step section gets one slot per step in the body:
> Shot slot: [Desktop] The "Broadcast" list in the admin panel. Include the "Create" button in the top right.
It states the device, the screen and what to include, so all that is left is to take that screenshot and swap it in. Slots are visible only in the editor, never to readers. Delete the slot once you have placed the image.
Layout mockups (optional)
Turn on "Insert a layout mockup automatically" (mockup_count) and Sorabun draws a wireframe showing only where things sit on the screen, based on the text in the shot slot. It keeps an article from going out with no images at all while the real screenshots are still pending.
Looking like the real thing is deliberately avoided. A how-to article is worth reading because people can compare it against what is in front of them, so a near-miss screen misleads them (a caption saying "top right" next to a drawing that puts it bottom left is the worst outcome). The image is a line drawing and always carries the note "this differs from the actual screen".
A real screenshot still serves readers better. Treat the mockup as a stand-in until you have one, not as a replacement: the shot slot stays in place, so you can swap both out together.
Off by default. Each image costs a generation fee.
Source citation
Each inserted image automatically gets a link to its source URL as a citation.
If you show another company's screen, you must satisfy the requirements for quotation (necessity, a clear primary/secondary relationship, and a stated source). The other party's terms of use may also prohibit posting screenshots. Always check before publishing.