DevTools • API Platforms • IPaaS

Keep your "Getting Started"
guides 100% accurate.

Stale screenshots in integration docs cause developer churn. Automate the capture of settings panels, API logs, and configuration screens directly from your test suite.

No credit card required•14-day free trial
~/project — zsh
❯npx poliage run
→ Reading docsync.config.json...
→ Launching headless browser...
→ Capturing 8 visuals...
✔api-keys-panel320ms
✔webhook-settings285ms
✔oauth-config312ms
✔api-logs-panel298ms
○integration-dashboard...
✓8 visuals captured successfully
Total time: 2.4s | Uploaded to CDN
The Problem

The "Hello World" Failure.

Developers judge the quality of a tool by the accuracy of its documentation. If a user follows a tutorial and the screenshot shows a configuration option that no longer exists, they lose trust in the platform stability. Manual screenshots cannot keep pace with daily shipping cycles.

Outdated screenshots signal an unstable product
Developers bounce when docs don't match reality
Daily deploys make manual updates impossible
Integration guides are the first touch point
documentation mismatch
DOCUMENTATIONSettingsMenuAPI KeyScreenshot shows API Key in sidebarACTUAL APP (v2.3)SettingsAPI KeyMenuAPI Key now in header (moved in v2.3)?
The Mechanism

Visuals as Code.

Stop treating screenshots as binary blobs in a folder. Define them as code scenarios. Poliage uses a docsync.config.json file to define exactly where to navigate and what to capture. This file lives in your repo, evolves with your codebase, and is reviewed like code.

Define visuals with selectors and test IDs
Version controlled with your source code
Review visual changes in pull requests
Roll back visuals with git revert
docsync.config.json
Visuals as Code
{
  "project": "acme-api-platform",
  "baseUrl": "http://localhost:3000",
  "visuals": [
    {
      "key": "api-keys-table",
      "path": "/settings/api-keys",
      "selector": "[data-testid='api-key-table']",
      "viewport": { "width": 1280, "height": 800 }
    },
    {
      "key": "webhook-config",
      "path": "/settings/webhooks",
      "action": "screenshot",
      "waitFor": ".webhook-list-loaded"
    },
    {
      "key": "oauth-flow",
      "path": "/integrations/oauth",
      "record": true,
      "steps": [
        "click:button.add-app",
        "fill:input.app-name:My App",
        "click:button.generate"
      ]
    }
  ]
}
The Workflow

Multi-Step "GIF" Automation.

Static images often fail to convey complex integration flows. Poliage allows you to record multi-step interactions and automatically generates optimized GIFs or MP4s on every commit. Show the full flow, not just the end state.

multi-step recording
Recorded Steps
1
Navigate to /api-keys→
2
Click "Generate Key"👆
3
Wait for modal⏳
4
Click "Copy"📋
5
Click "Close"✕
Generated Output
🎬
api-flow.mp4
12 frames • 4.2s
✓Generated: api-flow.mp4
✓Uploaded to CDN

Built for developer platforms

Features designed for teams shipping integration guides, API documentation, and developer tutorials.

Selector Targeting

Capture specific UI elements precisely.

data-testid support
CSS selector targeting
Dynamic wait conditions

Multi-Step Recording

Capture complex workflows as video.

Click, type, wait actions
GIF and MP4 output
Optimized file sizes

CI/CD Native

Run in your existing pipeline.

GitHub Actions integration
Docker-based execution
Parallel capture support

Ready to automate your dev docs?

Stop shipping tutorials with outdated screenshots. Generate accurate visuals on every commit and maintain developer trust.

No credit card required • 14-day free trial • Cancel anytime

Poliage Platform