melabidi/carmanagement
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity
Files
be30d19cdbddc3ffd254108223829b023c46fcfd
carmanagement/docs/project-design/PAGES.md
T
root 8aab968e09
Build & Deploy / Build & Push Docker Image (push) Successful in 1m2s
Details
Test / Type Check (all packages) (push) Failing after 28s
Details
Test / API Unit Tests (push) Has been skipped
Details
Test / Homepage Unit Tests (push) Has been skipped
Details
Test / Storefront Unit Tests (push) Has been skipped
Details
Test / Admin Unit Tests (push) Has been skipped
Details
Test / Dashboard Unit Tests (push) Has been skipped
Details
Test / API Integration Tests (push) Has been skipped
Details
Build & Deploy / Deploy to VPS (push) Successful in 3s
Details
refactor: rename marketplace to storefront across the entire monorepo 
Comprehensive rename of all marketplace references to storefront:
- API module: apps/api/src/modules/marketplace/ → storefront/
- Components: MarketplaceHeader → StorefrontHeader, MarketplaceShell →
  StorefrontShell, MarketplaceFooter → StorefrontFooter
- Types: marketplace-homepage.ts → storefront-homepage.ts
- Test files: employee-marketplace-* → employee-storefront-*
- All source code identifiers, imports, route paths, and strings
- Documentation (docs/), CI config (.gitlab-ci.yml), scripts
- Dashboard, admin, storefront workspace references
- Prisma field names preserved (isListedOnMarketplace, marketplaceRating,
  marketplaceFunnelEvent) as they map to database schema

Validation:
- API type-check: 0 errors
- Storefront type-check: 0 errors
- Dashboard type-check: 0 errors
- Full monorepo type-check: only pre-existing admin TS18046
2026-06-28 01:14:46 -04:00

4.6 KiB
Raw Blame History

Pages and Route Inventory — Current Apps

This document lists the pages that are actually present in the current frontend apps.

Source of truth:

  • apps/storefront/src/app
  • apps/dashboard/src/app
  • apps/admin/src/app

Storefront App

App:

  • apps/storefront

Public routes

  • /
  • /pricing
  • /features
  • /explore
  • /explore/[slug]
  • /review
  • /company-workspace
  • /platform-operations
  • /sign-in
  • /app-privacy-en
  • /app-privacy-fr
  • /app-privacy-ar
  • /app-tc-en
  • /app-tc-fr
  • /app-tc-ar
  • /footer/[slug]

Active route behavior

  • / is the public marketing home.
  • /pricing consumes platform pricing from /site/platform/pricing.
  • /explore is the public storefront search/discovery page.
  • /explore/[slug] is the company storefront profile page.
  • /review is the review submission page driven by a reservation review token.

Not present in the current storefront app

  • /about
  • /contact
  • /blog
  • /explore/[slug]/vehicles/[id]
  • a full company public-site booking frontend under its own app

Renter routes present in code but not active product entrypoints

These routes exist in the storefront app:

  • /renter/dashboard
  • /renter/notifications
  • /renter/profile
  • /renter/saved-companies
  • /renter/sign-in
  • /renter/sign-up

However:

  • /renter/sign-in redirects to the dashboard sign-in page
  • /renter/sign-up redirects to the dashboard sign-in page
  • API renter signup/login endpoints are disabled

Because of that, the renter self-service area should be treated as dormant or incomplete, not as an active supported user flow.

Dashboard App

App:

  • apps/dashboard

Base path:

  • /dashboard

Public/auth routes

  • /dashboard/sign-in
  • /dashboard/sign-up
  • /dashboard/forgot-password
  • /dashboard/reset-password
  • /dashboard/onboarding
  • /dashboard/onboarding/accept-invite

Private company workspace routes

  • /dashboard
  • /dashboard/fleet
  • /dashboard/fleet/[id]
  • /dashboard/reservations
  • /dashboard/reservations/new
  • /dashboard/reservations/[id]
  • /dashboard/online-reservations
  • /dashboard/customers
  • /dashboard/offers
  • /dashboard/team
  • /dashboard/reports
  • /dashboard/subscription
  • /dashboard/billing
  • /dashboard/contracts
  • /dashboard/contracts/[id]
  • /dashboard/reviews
  • /dashboard/complaints
  • /dashboard/notifications
  • /dashboard/settings

Route responsibilities

  • /dashboard shows KPIs and booking-source analytics.
  • /dashboard/fleet* manages vehicles, maintenance, and calendar blocks.
  • /dashboard/reservations* manages the booking lifecycle and inspection workflows.
  • /dashboard/online-reservations handles public/storefront booking intake.
  • /dashboard/customers is the company CRM view.
  • /dashboard/offers manages promotions.
  • /dashboard/team manages employees.
  • /dashboard/reports shows analytics/reporting views.
  • /dashboard/subscription manages SaaS plan state and invoices.
  • /dashboard/billing manages rental payment collection and balances.
  • /dashboard/contracts* opens rental contracts.
  • /dashboard/reviews and /dashboard/complaints handle post-rental follow-up.
  • /dashboard/notifications shows notification inbox/history/preferences.
  • /dashboard/settings manages brand, domains, policies, insurance, pricing, and accounting settings.

Admin App

App:

  • apps/admin

Public routes

  • /
  • /login
  • /forgot-password
  • /reset-password
  • /auth-redirect

Private admin dashboard routes

  • /dashboard
  • /dashboard/companies
  • /dashboard/companies/[id]
  • /dashboard/renters
  • /dashboard/admin-users
  • /dashboard/audit-logs
  • /dashboard/billing
  • /dashboard/pricing
  • /dashboard/notifications
  • /dashboard/site-config
  • /dashboard/containers

Route responsibilities

  • /dashboard is the admin overview.
  • /dashboard/companies* manages tenant companies.
  • /dashboard/renters inspects and blocks/unblocks renter accounts.
  • /dashboard/admin-users manages admin operators.
  • /dashboard/audit-logs reviews admin activity.
  • /dashboard/billing manages platform billing operations.
  • /dashboard/pricing edits platform pricing, features, and promotions.
  • /dashboard/notifications inspects platform notifications.
  • /dashboard/site-config edits storefront/site configuration content.

Deliberately Not Listed

This document excludes:

  • API endpoints
  • dormant backend-only concepts that do not have an active frontend route
  • design-spec routes that are not present in the current app trees

For backend route inventory, use:

  • docs/project-design/api-routes.md
Reference in New Issue View Git Blame Copy Permalink