Screenshots: Stripe payment gateway walkthrough (13 placeholders)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 63/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Domain
- documentation, payments
Research direction
Start by reading docs/user-guide/payment-gateways/stripe.md and use the listed Ultimate Multisite and Stripe Dashboard test-mode screens as the capture sources. Add the 12 specified PNGs at 1280×800, crop each to its control, keep each under 200 KB, redact all keys, and update every referenced image path and alt text. Done means the checklist is complete without deleting settings-payment-gateways.png.
Written by the indexing model from the issue text.
Description
For #64.
Problem
docs/user-guide/payment-gateways/stripe.md references 13 distinct concepts but every image points to /img/config/settings-payment-gateways.png. Worse, most steps describe screens on dashboard.stripe.com (not WordPress at all).
docs/user-guide/payment-gateways/stripe.md
L16 
L22 
L26 
L34 
L38 
L42 
L46 
L48 
L56 
L60 
L64 
L68 
Captures required
Mixed source: Ultimate Multisite admin (wordpress.local:8080) and the Stripe Dashboard in test mode (https://dashboard.stripe.com/test). Use a Stripe test account — never capture live keys.
Crop tightly so each shot points at exactly one control. Redact any real keys with a black bar before saving.
| # | Doc line | Where | New filename |
|---|---|---|---|
| 1 | L16 | UM → Settings → Payments — Active Payment Gateways with Stripe toggle on | static/img/payment-gateways/stripe/um-enable-gateway.png |
| 2 | L22 | Front-end checkout showing inline Stripe card field | static/img/payment-gateways/stripe/inline-card-field.png |
| 3 | L26 | Front-end checkout redirecting to Stripe Checkout | static/img/payment-gateways/stripe/checkout-redirect.png |
| 4 | L34 | UM Stripe gateway settings — API key fields + Sandbox toggle | static/img/payment-gateways/stripe/um-api-keys-form.png |
| 5 | L38 | Stripe Dashboard → Developers → API keys | static/img/payment-gateways/stripe/dashboard-developers.png |
| 6 | L42 | Stripe Dashboard Viewing test data toggle highlighted | static/img/payment-gateways/stripe/dashboard-test-mode.png |
| 7 | L46 | Stripe Dashboard API keys with Publishable + Secret revealed (redact) | static/img/payment-gateways/stripe/dashboard-keys.png |
| 8 | L48 | UM Stripe form with the keys pasted in (redact) | static/img/payment-gateways/stripe/um-keys-pasted.png |
| 9 | L56 | Stripe Dashboard → Developers → Webhooks with + Add endpoint highlighted | static/img/payment-gateways/stripe/dashboard-webhooks.png |
| 10 | L60 | UM Stripe form — Webhook Listener URL field highlighted | static/img/payment-gateways/stripe/um-webhook-url.png |
| 11 | L64 | Stripe Dashboard endpoint setup with the URL pasted | static/img/payment-gateways/stripe/dashboard-endpoint-paste.png |
| 12 | L68 | Stripe Dashboard endpoint creation with Receive all events chosen | static/img/payment-gateways/stripe/dashboard-receive-all.png |
Capture at 1280×800. After cropping to the panel, save < 200 KB.
Doc edit
Update every line in docs/user-guide/payment-gateways/stripe.md to its new path above.
Do not delete settings-payment-gateways.png — it’s still referenced by docs/user-guide/payment-gateways/getting-paid.md, manual-payments.md, the-registration-flow.md, and several addon docs.
Done when
- All 12 new PNGs added under
static/img/payment-gateways/stripe/. -
docs/user-guide/payment-gateways/stripe.mdupdated with correct paths and alt text. - No real Stripe keys are visible in any committed image.
- PR opened with
Resolvesfor this issue andRef #64.
aidevops.sh v3.15.64 plugin for OpenCode v1.15.5 with claude-sonnet-4-6 spent 4d 9h and 383 tokens on this as a headless worker.
- Dominant language
- MDX
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Ultimate-Multisite/docs
-
documentation needs-update origin:interactive status:available
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
Ultimate-Multisite/docs#187 ·
-
documentation needs-update origin:interactive tier:standard
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Ultimate-Multisite/docs#182 · 1 comment ·
-
documentation needs-update origin:interactive
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Ultimate-Multisite/docs#173 ·
-
documentation needs-update origin:interactive tier:standard
Difficulty 3/5 1-2 days Newbie friendliness 72/100
Ultimate-Multisite/docs#186 · 1 comment ·
-
auto-dispatch documentation needs-update origin:interactive status:available tier:standard
Difficulty 3/5 1-2 days Newbie friendliness 84/100
Ultimate-Multisite/docs#185 ·
All issues in Ultimate-Multisite/docs
Similar issues
-
sync-en
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
-
affects/8.7 affects/8.8 affects/8.9
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
camunda/camunda-docs#9997 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 75/100
sillsdev/languageforge-lexbox#2665 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
area:tools priority:p2 type:bug
Difficulty 1/5 Under an hour Newbie friendliness 91/100
amichai-bd/nand2mario#939 ·