Reshotdocs

For Docs & Support Teams

This guide is for the people who own the docs, help center, and support content — not engineers. Once your engineers wire capture into CI one time, everything below is yours to run. You never touch a terminal, a repo, or a line of code.

Your one screen: the Review Queue

When the product changes and a screenshot drifts, Reshot captures the new version and drops it into the Review Queue as a candidate. That queue is the only screen you need.

You seeWhat it means
Old → NewThe previously approved image next to the freshly captured one
DiffWhat actually changed, highlighted, so you can decide in seconds
PENDINGWaiting for your approval
APPROVEDLive — every place that embeds this visual is now current

Approving a change

  1. Open CLI Commits (or Review Queue) in your project dashboard.
  2. Filter to Pending Reviews.
  3. For each candidate, compare old vs. new and the diff.
  4. Click Approve (✓) to publish it, or Reject (✗) to keep the current image.

That's it. When you approve, the stable URL for that visual starts serving the new image everywhere it's embedded — your docs, help center, changelog, and launch posts — with no redeploy and no engineering ticket.

Why you don't need engineers for this

  • No repo access. Capturing happens in your engineers' environment; you only ever see the resulting candidates.
  • No CLI. Approving and rejecting are buttons in the dashboard.
  • No redeploy. Approval flips the live pointer instantly — the embedded URL stays the same, only the image behind it updates.
  • No filename juggling. You never swap a PNG by hand; each visual has one durable reference that you keep current from this one screen.

A typical week

  1. Engineers ship product changes (as they always do).
  2. Reshot captures the drifted screenshots in CI and files them as candidates.
  3. You open the Review Queue, approve the good ones, reject the rest.
  4. Your help center stays accurate — without a single support ticket about a stale screenshot.