Rename legacy storefront app and references to carplace
Build & Push / Build & Push Docker Image (push) Failing after 10m39s

Replace storefront naming across source, tests, docs, config, and production scripts. Rename the legacy top-level app directory and Carplace component files, remove duplicate storefront startup scripts, and refresh the lockfile.
This commit is contained in:
root
2026-07-04 18:10:08 -04:00
parent fefaf8108d
commit c77d0a8e89
113 changed files with 366 additions and 434 deletions
+7 -7
View File
@@ -4,7 +4,7 @@ This document lists the features that are active in the current codebase.
Source of truth:
- `apps/storefront`
- `apps/carplace`
- `apps/dashboard`
- `apps/admin`
- `apps/api`
@@ -14,7 +14,7 @@ Source of truth:
The current workspace contains four active apps:
- `apps/storefront`
- `apps/carplace`
- `apps/dashboard`
- `apps/admin`
- `apps/api`
@@ -61,12 +61,12 @@ There is no separate frontend app for a white-label company public site in this
- Notification inbox and preferences
- Subscription management
### Storefront and public platform
### Carplace and public platform
- Public marketing homepage
- Public pricing page
- Public features page
- Public storefront/explore flow
- Public carplace/explore flow
- Explore company profile pages under `/explore/[slug]`
- Public review submission page via review token
- Public legal/app policy pages
@@ -120,7 +120,7 @@ There is no separate frontend app for a white-label company public site in this
- Billing operations
- Pricing configuration and promotions
- Notification review
- Storefront/site config management
- Carplace/site config management
## Present But Not Active Product Features
@@ -144,9 +144,9 @@ The following old design ideas should not be treated as active features unless c
- standalone about/contact page set
- Google renter auth
- automatic custom-domain provisioning
- Zapier/webhook storefront integrations beyond the current API/webhook handlers
- Zapier/webhook carplace integrations beyond the current API/webhook handlers
## Notes
- The database still contains legacy fields such as `Employee.clerkUserId`, but those fields are no longer evidence of active Clerk integration.
- Some renter-facing `/renter/*` pages exist in the storefront app, but the auth entrypoints they depend on are not active. They are therefore not listed as active product scope here.
- Some renter-facing `/renter/*` pages exist in the carplace app, but the auth entrypoints they depend on are not active. They are therefore not listed as active product scope here.