Media inventory

Every screenshot, video and diagram the documentation calls for, ordered by priority rather than by filename.

59 placeholders: 58 screenshots, 1 video.

Each one appears inline in the docs as a greppable comment:

<!-- MEDIA: screenshot | id: example-placeholder-id | description -->

To find one in the source:

grep -rn "id: install-snippet-copy" docs/

To find everything still outstanding:

grep -rn "MEDIA:" docs/

Capture conventions

Apply to everything unless a row says otherwise.

Priority 1 — blocking getting-started and install

These are the pages a new customer reads in their first five minutes. Nothing else matters until these exist.

1a. The first-run flow

1b. The install-page snippet tabs

Six shots of the same screen with a different platform tab selected. Capture them in one sitting — same account, same site, same key, same crop — so they read as one set.

All: 1440px, light.

1c. Verification

Priority 2 — third-party platform UIs

Screens inside someone else's product. Each needs a real account on that platform, which makes them the slowest to produce — start acquiring accounts early even though they rank second.

Keep each platform's own theme; do not force light on a product whose UI is dark.

Priority 3 — the dashboard

One populated test site can produce almost all of these in a single session. Seed it with about a month of varied traffic — several countries, several referrers, a mix of browsers, and a decent spread of crawler families — then capture in one pass so the numbers agree across every shot.

Priority 4 — the AI panel

The product's differentiator. Same seeded site as Priority 3, with a realistic crawler mix.

Priority 5 — troubleshooting and error states

Every one of these is a failure state, so each has to be produced deliberately against a test site. Several cannot be captured by chance.

Priority 6 — features not yet built

Do not attempt these until the feature ships. Each is listed against the page that will need it, so nothing is forgotten at launch.

Sharing

#50 is the important one — the page's whole promise is "here is exactly what your viewer sees", so it must be captured in a genuinely signed-out browser rather than approximated.

Team

API

Billing

Batching plan

Roughly how to sequence a capture session.

Blockers worth knowing before you start

#27 dashboard-four-tiles and #37/#39 (the AI panel) — IP verification is not running yet, so a live capture shows "Verified crawlers" as 0%. Either seed verified rows, or accept the 0% and re-capture when verification ships. Do not retouch the number.

#54–57 (billing) — the billing screens are not built. The pricing page may be; check before deferring #54.

#49–53 (sharing, team, API) — those screens do not exist yet.

#46 proxy-broken-ip-symptom — this one has to be manufactured. Stand up a proxy that deliberately drops the client IP, point a test site at it, generate traffic from a few different addresses, and capture the collapse. It is the most effort of any single image here and it is also the one that stops a customer destroying their own visitor counts.