groombook/app
Archived
13
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Flip routing: customer portal at /, admin at /admin #56

New Issue
Closed
opened 2026-03-19 02:05:47 +00:00 by ghost · 0 comments
ghost commented 2026-03-19 02:05:47 +00:00 (Migrated from github.com)
Copy Link
Copy Source

Context

Asking customers to navigate to /portal is a non-starter (ref: GRO-47). The customer-facing experience should live at the root URL.

Decision

Flip the routing:

  • Customer portal → / (root) — this is what customers see when they visit the business URL
  • Staff admin → /admin/* — staff navigate here to manage appointments, clients, etc.

This gives customers clean, shareable booking links (groomer.com/ instead of groomer.com/portal) while staff simply bookmark /admin.

Implementation

  1. Move all current admin routes under /admin prefix (appointments, clients, services, staff, invoices, group-bookings, reports, book)
  2. Mount the customer portal at / (root)
  3. Update the admin nav links to include the /admin prefix
  4. Keep the "Customer Portal" link in admin nav pointing to / so staff can preview what customers see
  5. Update any existing tests/e2e that reference the old paths

Notes

  • Subdomain support (e.g., portal.groomer.com vs admin.groomer.com) is a future enhancement, not needed now
  • No auth changes needed for this PR — just routing
## Context Asking customers to navigate to `/portal` is a non-starter (ref: GRO-47). The customer-facing experience should live at the root URL. ## Decision Flip the routing: - **Customer portal** → `/` (root) — this is what customers see when they visit the business URL - **Staff admin** → `/admin/*` — staff navigate here to manage appointments, clients, etc. This gives customers clean, shareable booking links (`groomer.com/` instead of `groomer.com/portal`) while staff simply bookmark `/admin`. ## Implementation 1. Move all current admin routes under `/admin` prefix (appointments, clients, services, staff, invoices, group-bookings, reports, book) 2. Mount the customer portal at `/` (root) 3. Update the admin nav links to include the `/admin` prefix 4. Keep the "Customer Portal" link in admin nav pointing to `/` so staff can preview what customers see 5. Update any existing tests/e2e that reference the old paths ## Notes - Subdomain support (e.g., `portal.groomer.com` vs `admin.groomer.com`) is a future enhancement, not needed now - No auth changes needed for this PR — just routing
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something isn't working
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 feature
New feature
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 question
Further information is requested
 wontfix
This will not be worked on
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
ai-review (AI Review) gb_barkley (Barkley Trimsworth) cpfarhood (Chris Farhood) ci (Continuous Integration [bot]) gb_flea (Flea Flicker) flux (Flux CD) admin (Gitea Admin) gb_lint (Lint Roller) renovate (Mend Renovate) gb_pawla (Pawla Abdul) gb_scrubs (Scrubs McBarkley) gb_shedward (Shedward Scissorhands) gb_dogfather (The Dogfather)
No Assignees
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: groombook/app#56
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?