Documentation coverage and verification
This edition covers both websites. Use Production documentation or New staging documentation to enter the correct version. Labels and actions are separated inside each shared guide. Staging-only workspaces are marked explicitly.
Workflows covered
Section titled “Workflows covered”| Role or task | Guides |
|---|---|
| Visitors | Navigation, directories and filters, public school/teacher/event profiles, community events, policies, contact and feedback |
| Members | Sign up, sign in, password recovery, profile and password changes, messages, notifications, reviews, billing and receipts |
| School applicants | School information, yoga/faculty, designation and membership choice, documents, consent, payment, approval and license status |
| Teacher applicants | Personal and yoga information, designation, experience, documents, consent, payment, approval and license status |
| School and teacher owners | Public profile, contact visibility, social links, images, gallery, school graduates and license status |
| Event organizers | All editor steps, media, instructors, formats/facilities, update and renewal, approval, attendee search/details and booking actions |
| Event participants | Find, book, participant details, price/payment, booking outcome and version-specific cancellation/refund steps |
| New staging member tools | My event bookings, saved events, referrals/commissions, organizer payouts and internal courses |
| New staging school tools | Add-on courses, certificate template design, activation, graduate issuance, PDF/public verification and revocation |
| New staging staff | Sign in/roles, dashboard/queues, school/teacher/member records, moderation and imports, events/bookings, community events, content/SEO/translations, certificates, invoices/orders, reconciliation, affiliates/payouts, system settings, audit and reference data |
| Production staff | Django backoffice sign in, lists/filters, directory and registration records, event/booking records, invoices and content administration |
External Resources & Store services have their own website and account/payment rules. These guides explain the WYA link and boundary; they do not document an uninspected external store.
How this edition was checked
Section titled “How this edition was checked”Reviewed on 8 October 2026 against the production Vue application and the new staging application. Authenticated read-only browser checks sampled production and staging registration entry/information, owner profile, event creation, organizer event lists and billing; staging member bookings, referrals, courses and directory filters were also inspected. A separate read-only staging staff session checked the dashboard and main people, operations, content, commerce, system, certificate, affiliate and reference workspaces. Source review supplied controls behind later workflow steps and role-specific screens.
The documentation build checks each page’s heading, description and canonical URL, all internal links and section anchors, sitemap and search files. A route inventory in the documentation repository maps the website pages to guides, so public and protected screens are included in the coverage review.
Verification limits
Section titled “Verification limits”No application, document upload, event, attendee, payment, payout, certificate or staff record was submitted or changed to write these guides. Administrative and later transaction steps are source-reviewed instructions, not proof of a completed hosted transaction. Hosted payment methods, fees, cancellation windows and eligibility can change; use the amounts and eligibility shown on your screen and the published policy.
Production and staging have different routes, data and permissions. A successful payment, approved registration, published event and confirmed booking are separate outcomes. Where a member control does not exist in a version, the guide directs you to the organizer or WYA rather than inventing a button.
If a label differs, check your version, language and role and use Contact WYA. Include the page and displayed message, without passwords or another person’s private information.