Appearance
Routes Not Critical to Core Functionality
Which admin and portal routes are not required for day-to-day member and staff workflows. Use this for prioritization, docs, or hiding non-essential nav.
Not Critical to Core Functionality
Admin — Clearly Non-Critical (Dev / Staging / One-Time)
| Route(s) | Why not critical |
|---|---|
/admin/testing (and time-machine, reset, cleanup, scenarios/memberships) | Testing Suite: “Simulate scenarios, manipulate data, and test workflows safely.” Test mode blocks real emails and is for QA/staging. Not needed for normal production use. |
/admin/system/wordpress, /admin/sync/wordpress, /admin/sync/wordpress-events | WordPress migration/sync: moving events and users from WP into UI Engine. Important during cutover; after that it’s occasional or one-time. |
/admin/system (System Dashboard) | Overview of LGL/WP/queue. Helpful for ops, but core member flows (join, pay, enroll) don’t depend on staff opening it. |
/admin/system/queue | Sync queue visibility. Sync runs in the background; staff don’t need this for daily operations. |
/admin/logs (legacy: /admin/system/logs → redirect) | Audit logs for compliance/debugging. Not part of the main user journey. |
/admin/email-log | Email log for debugging. Not required for core flows. |
Admin — Only Critical for Some Orgs
| Route(s) | When they’re not critical |
|---|---|
/admin/donations (list/detail/new) | If the org doesn’t run donations through this app. |
/admin/coupons | If they don’t use discount codes. |
/admin/import, /admin/import/history | If classes are created manually or via templates rather than bulk import. |
/admin/inventory | If they don’t track product/class inventory. |
/admin/products/templates, /admin/products/templates/new | If they manage products without using templates. |
/admin/messaging/campaigns (and edit/new) | If member communications are done elsewhere (e.g. Mailchimp). |
/admin/settings/assets, /admin/settings/emails, /admin/settings/lgl | Configuration; only needed when changing settings, not for daily member-facing functionality. |
Portal — Only Critical for Some Flows
| Route(s) | When they’re not critical |
|---|---|
/portal/auth/claim (and admin /auth/claim) | Only if you don’t use magic-link or invite-claim flows. |
/portal/invitation/[token] | Only if you don’t use family/invitation flows. |
/portal/events/track, /portal/events/track/[token] | Only if you don’t need event submission tracking/analytics. |
/portal/events/submit | The “Submit test event” path is dev-only; the page can still be used for real submissions. |
/portal/checkout/scholarship, /portal/membership/scholarship | Only if you don’t offer scholarships through the app. |
Critical to Core Functionality (Summary)
- Portal:
/,/login,/register,/account(and main account subpages),/membership,/membership/[tier],/checkout,/checkout/success,/classes,/classes/[id],/events,/events/[id],/account/enrollments,/account/registrations,/account/family,/account/settings/*,/unsubscribe/[token](compliance). - Admin: Dashboard, members, memberships, membership-levels, payments, users, classes, semesters, enrollments, events, registrations, products (list/detail and key subpages), instructors, scholarship-requests (if you use scholarships), settings (main + roles), LGL sync hub, email templates. Plus auth:
/login,/reset-password,/auth/reset-password.
The Testing Suite, WP Migration/sync, System/queue/logs, and email-log are the ones that are clearly not critical to day-to-day functionality; the rest of the “not critical” list depends on whether you use donations, coupons, import, inventory, templates, messaging, claim/invite, event tracking, or scholarships.