feat: prepare CMS pages for deployment
This commit is contained in:
@@ -22,7 +22,7 @@ This project is being tightened toward launch as a CMS-first Eversolo brand site
|
||||
- Keep Payload globals and collections broad enough for editors, but avoid showing implementation-only legacy fields in admin.
|
||||
- Prefer compact admin groups, list-style arrays, and explicit per-locale documents for user-facing content.
|
||||
- Re-run `npm run generate:types`, `npm run build`, and the smoke check after schema or cache changes.
|
||||
- After restarting a local preview, check both `/en` and `/zh` for homepage, product detail, downloads, news, dealers, support, and admin access.
|
||||
- After restarting a local preview, check both `/en` and `/zh` for homepage, product detail, downloads, news, where-to-buy, support, and admin access.
|
||||
|
||||
## Deployment Discipline
|
||||
|
||||
|
||||
Reference in New Issue
Block a user