consolidated: screenshot audit and refresh program

Treat this as the program tracker; implementation is assigned to child issues #65–#77 and #84–#96, with #85 checking reusable orphan assets before recaptures. Start by reading the relevant child issue and its named documentation page and image paths, then follow the capture standards in this issue. Done means the child work meets its acceptance criteria and has a PR; this tracker covers a repository-wide program and is not a suitable standalone first contribution.

Supersedes #64 — this issue is the consolidated spec.

What

Run the repository-wide Screenshot Audit and Refresh Program. Every documentation screenshot must depict the UI described beside it, be unique to that concept, tightly cropped to the relevant control, readable, and optimized for the documentation site. Deliver the work through the already-filed child issues; retain this issue as the program tracker.

Program inventory and delivery structure

• The English docs currently track 147 image files, reference 98 unique image paths, and include at least 32 byte-identical duplicate files.
• Existing focused children remain the implementation queue: #65 Zapier, #66 Stripe, #67 PayPal, #68 customer account, #69 product limitation tabs, #70 network dashboard widgets, #71 payment tabs, #72 checkout editor, #73 registration form (after #72), #74 webhooks, #75 installation wizard, #76 analytics dashboard, #77 site templates.
• The second audit added children #84 (28 addon index.mdx pages with no screenshots), #85 (48 unreferenced static/img/ files; examine reusable captures before recapturing), and #86–#96 for the gap pages listed in How.
• Keep #64 as the historical source, but use this issue as the single current specification. Issues #78–#83 were duplicate section programs and remain superseded; do not reopen them.
• Lower-priority, not-yet-filed work: re-capture the populated-list states in docs/user-guide/administration/touring-the-admin-panel.md and docs/user-guide/administration/managing-memberships.md with seed data.

Why

The audit found screenshots reused for unrelated concepts, including walkthroughs where one placeholder illustrates every step. This makes instructions misleading, conceals current product UI, and adds unnecessary static assets. The program replaces placeholders with accurate shots, wires in useful orphan captures before taking new ones, and keeps images fast and consistent.

How

Capture and asset standards

Capture against the current Ultimate Multisite main build in the authorized local WordPress environment. Use authorized credentials without recording them in commits, comments, screenshots, or issues. Standard tools include Flameshot/GNOME Screenshot, macOS Screenshot, or a headed Playwright/Chromium window configured to the capture viewport. Rename macOS screenshots to ASCII before committing; the default name can contain a narrow no-break space. Do not retain default Screenshot … AM/PM.png names.

Per-child workflow

1. Re-create or open the screen described by the target documentation text.
2. Capture to the exact existing asset path, or add the narrowly named new asset path stated by the child issue.
3. For a split walkthrough, update the listed Markdown/MDX references to the new per-step captures.
4. Optimize the image, run npm start, visit the target documentation page, and verify every image renders and matches the adjacent text.
5. Commit with docs(screenshots): refresh <area> per issue #<N> and open a PR for the child issue.

Audit findings and assigned children

Exact duplicate asset groups

The following MD5-equal groups must become concept-specific captures through their assigned children:

Placeholder walkthroughs already covered

• #65: docs/user-guide/integrations/zapier.md has 14 distinct Zapier concepts but uses webhooks-list.png; it needs the dashboard, app search, trigger picker, auth, Ultimate Multisite API settings, credentials, payment_received, test step, action setup, and the other described steps.
• #66: docs/user-guide/payment-gateways/stripe.md has 13 concepts but repeatedly uses settings-payment-gateways.png; cover active gateways, inline card, Checkout redirect, keys, Stripe dashboard, test data, webhooks, listener URL, and endpoint setup.
• #67: docs/user-guide/payment-gateways/paypal.md has 5 concepts but reuses the payment settings image for PayPal-side steps.
• #68: docs/user-guide/client-management/account-page.md has 16 customer-facing account concepts but reuses network-admin images. Cover account menu/overview, plan, limits, billing, profile update, template switching, domain/DNS flow, password, and Danger Zone.
• #74: replace the heavy /img/admin/webhooks-list.png placeholder reuse in the Zapier registration/webhook flow.

High-reuse images and the corresponding program work

/img/admin/webhooks-list.png is referenced 35 times (#65, #74); /img/config/settings-payment-gateways.png 34 times (#66, #67); /img/admin/memberships-list.png 17 times; /img/config/checkout-form-step.png 16 times (#72, #73); /img/config/settings-taxes.png 15 times; and /img/config/discount-codes-list.png 14 times. The last four are resolved by the child issues below or future focused work, not by a blanket asset replacement.

Gap-page children from the second audit

Use these exact page-level findings when executing #86–#96. The line references were recorded on the audit revision; verify current context before editing.

Additional program scope and decisions

• #84 owns the 28 addon index pages with no screenshots.
• #85 owns the 48 orphan static images; use accurate existing images before creating replacements, particularly for #89, #95, and #87.
• Future focused issues may cover VAT/tax, discount codes, domain mapping, WooCommerce, GoCardless, PayFast, Language Selector, Site Exporter, Admin Page Creator, and administration-tour refreshes when not already covered above.
• Do not reopen #78 (duplicate master), #79 (covered by #65/#74), #80 (covered by #66/#67/#71 and #86–#88), #81 (covered by #69/#72/#73/#77 and #89/#90), #82 (covered by #68 and #91–#94), or #83 (covered by #95/#96 plus the future list-state refresh).

Audit reproducibility

Use the following checks when reassessing a target area:

git ls-files | grep -iE '\.(png|jpg|jpeg|gif|webp)$'
find static/img -type f -name '*.png' -exec md5sum {} \; | sort | uniq -d -w 32
grep -rohE '/img/[^)" ]+\.png' docs/ | sort | uniq -c | sort -rn
find static/img -name '*.png' -exec file {} \;

Acceptance Criteria

• Each child issue has an accurate, per-concept capture plan; no implementation PR reuses a known placeholder image for a materially different UI state.
• New/replaced screenshots meet the capture standards, optimize their PNGs, and render correctly in the relevant documentation page.
• The duplicate groups and per-page placeholder work are completed only through their focused child issues, with #85 assessed before recapturing candidate orphan assets.
• The screenshot program retains the documented child-issue coverage and does not reopen superseded duplicate programs #78–#83.
• The two populated-list refresh pages remain explicitly deferred until separately filed.

Context & Decisions

• Original audit / #64: established the asset counts, duplicate groups, capture standards, child #65–#77 queue, and original future-work candidates. Its core decision was one focused issue per screenshot area rather than a monolithic asset change.
• @superdav42, Comment 1: reported a parallel duplicate audit (#78/#79/#80), added the zero-screenshot addon and orphan-file categories, and recommended retaining the #64 program with focused children rather than parallel section trackers.
• @superdav42, Comment 2: reconciled the two methodologies, recorded 11 additional placeholder-reuse pages and two data-state pages, retained #84/#85 as net-new issues, and confirmed #78–#83 were duplicates.
• @superdav42, Comment 3: confirmed that the 11 gap pages were filed as #86–#96 and supplied the complete index tying every affected page to its focused child. This supersedes the earlier proposal to create those children.
• Final agreed approach: this single issue is the program specification; execute focused children, reuse accurate orphan assets where possible, and keep capture operations reproducible and optimized.

Contributors

cc @superdav42

Files Scope

Hard boundaries: This is a coordination tracker. It authorizes no direct repository-file changes; source and asset edits belong only to the explicitly linked child issues.

AI brief owner: Pulse consolidation workflow.

aidevops.sh v3.34.13 plugin for OpenCode v1.18.31 with gpt-5.6-terra