feat(tour): add onboarding tours for various admin pages
- Integrated TourButton component into SettingsMenuPage, SkillsPage, SmsWalletPage, StaffPage, StaffSessionDetailPage, StaffTreatmentSessionsPage, SubscriptionPage, TagsSettingsPage, TreatmentCasesPage to enhance user onboarding experience. - Created new tour definitions for appointments, clinics, staff management, financial management, and patient management, ensuring comprehensive guidance for users navigating the admin panel. - Updated documentation to reflect the addition of tours and their implementation details.
This commit is contained in:
@@ -200,6 +200,14 @@ Each tour carries a `version` in the frontend registry (`assets/admin/lib/tour/t
|
||||
The tour auto-runs again when its version is higher than the stored one, which is how a rewritten
|
||||
tour reaches users who already saw the old text.
|
||||
|
||||
Every non-admin page of the panel ships a tour. Adding one to a new page means: a file under
|
||||
`assets/admin/lib/tour/tours/`, one line in `registry.ts`, and `tourId` on the page's `PageHeader`
|
||||
— the shared `data-tour` anchors (`page-title`, `page-action`, `page-search`, `page-table`,
|
||||
`page-pagination`) already come from `PageHeader`, `DataTable` and `Pagination`. A step whose
|
||||
anchor is not on screen is dropped silently, so role-specific pages need no branching.
|
||||
`PageHeader` auto-runs the tour once the page is ready; pass `tourReady={!isLoading}` when the
|
||||
data arrives late.
|
||||
|
||||
## GET `/api/v1/my/tours`
|
||||
|
||||
Tours the current user has already been through.
|
||||
|
||||
Reference in New Issue
Block a user