For #64.
Problem
docs/user-guide/configuration/the-registration-flow.md references 9 distinct concepts across four recycled images. The doc walks the entire end-to-end customer registration → site provisioning → manual-payment-confirmation flow, but every image is either a generic checkout-form admin shot or the admin payments list.
docs/user-guide/configuration/the-registration-flow.md
L20 
L26 
L32 
L46 
L50 
L54 
L60 
L64 
L66 
L70 
Most of this is frontend UI captured from a non-admin browser session — captures must come from the registration / customer-facing flow, not Network Admin.
Captures required
Setup: ensure the test site has at least one product visible on the registration page, the Manual gateway is enabled with payment instructions filled in, and you can complete a registration as a fresh customer.
| # |
Doc line |
Capture target |
New filename |
| 1 |
L20 |
Frontend /register page showing the active checkout form |
static/img/frontend/registration-form.png |
| 2 |
L26 |
"Thank You" / order-received page after registration |
static/img/frontend/registration-thank-you.png |
| 3 |
L32 |
Site-activated confirmation with "Sign in to your dashboard" link |
static/img/frontend/site-activated.png |
| 4 |
L46 |
Frontend checkout step displaying the Manual-payment notice |
static/img/frontend/registration-manual-notice.png |
| 5 |
L50 |
Post-registration page showing the manual payment instructions |
static/img/frontend/registration-payment-instructions.png |
| 6 |
L54 |
Admin: Manual gateway toggle + Payment Instructions field in Settings → Payments — share with issue for manual-payments.md if filed |
static/img/config/manual-gateway-settings.png |
| 7 |
L60 |
UM → Payments list with the new pending manual payment row |
reuse static/img/admin/payments-list.png once seeded |
| 8 |
L64 |
Single payment detail page for the pending manual payment |
static/img/admin/payment-edit.png (orphan exists — verify and wire in) |
| 9 |
L66 |
Payment edit page with Status → Completed option selected |
static/img/admin/payment-status-completed.png |
| 10 |
L70 |
Payment edit page showing Activate Membership toggle + Save Payment button |
share with manual-payments.md issue → static/img/admin/payment-activate-membership.png |
Capture at 1280×800, crop to the relevant card. Frontend captures should be from a guest / non-admin browser. < 200 KB.
Doc edit
Update every line in docs/user-guide/configuration/the-registration-flow.md to its new path and refine alt text. Where a capture is shared with another gap issue (manual-payments.md), use the same filename so both docs reference one canonical file.
Done when
For #64.
Problem
docs/user-guide/configuration/the-registration-flow.mdreferences 9 distinct concepts across four recycled images. The doc walks the entire end-to-end customer registration → site provisioning → manual-payment-confirmation flow, but every image is either a generic checkout-form admin shot or the admin payments list.Most of this is frontend UI captured from a non-admin browser session — captures must come from the registration / customer-facing flow, not Network Admin.
Captures required
Setup: ensure the test site has at least one product visible on the registration page, the Manual gateway is enabled with payment instructions filled in, and you can complete a registration as a fresh customer.
/registerpage showing the active checkout formstatic/img/frontend/registration-form.pngstatic/img/frontend/registration-thank-you.pngstatic/img/frontend/site-activated.pngstatic/img/frontend/registration-manual-notice.pngstatic/img/frontend/registration-payment-instructions.pngmanual-payments.mdif filedstatic/img/config/manual-gateway-settings.pngstatic/img/admin/payments-list.pngonce seededstatic/img/admin/payment-edit.png(orphan exists — verify and wire in)static/img/admin/payment-status-completed.pngmanual-payments.mdissue →static/img/admin/payment-activate-membership.pngCapture at 1280×800, crop to the relevant card. Frontend captures should be from a guest / non-admin browser. < 200 KB.
Doc edit
Update every line in
docs/user-guide/configuration/the-registration-flow.mdto its new path and refine alt text. Where a capture is shared with another gap issue (manual-payments.md), use the same filename so both docs reference one canonical file.Done when
static/img/frontend/,static/img/config/, andstatic/img/admin/.docs/user-guide/configuration/the-registration-flow.mdupdated.Resolvesfor this issue andRef #64.