pukpuklouis/website-enchun-mgr
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: regenerate tasks.md to align with corrected route structure

Browse Source
This commit is contained in:
Louis Chen
2025-09-22 16:49:16 +08:00
parent b297dedf2c
commit e7747c1c3e
14 changed files with 143 additions and 209 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
PRD.md
View File

@@ -67,6 +67,7 @@ The application will feature a clear separation between public and protected rou
* **Styling:** The project will use **Tailwind CSS**.
* **Accessibility:** The site must adhere to WCAG 2.1 AA standards.
* **Deployment:** The Astro frontend will be deployed on **Cloudflare Pages** in SSR (Server-Side Rendering) mode to support the authentication layer. The Payload CMS backend and serverless functions will run on **Cloudflare Workers**.
* **Workspace Layout:** Monorepo managed with **pnpm** workspaces. Packages include `frontend/` (Astro), `backend/` (Payload CMS), and `packages/shared/` for cross-cutting TypeScript utilities.
**6. Technology Stack**
@@ -80,9 +81,10 @@ The application will feature a clear separation between public and protected rou
**7. Migration Plan (High-Level)**
1. **Phase 1: Project Setup**
* Initialize a new Astro project configured for SSR.
* Set up Payload CMS for Cloudflare Workers.
* Configure Tailwind CSS.
* Initialize a pnpm workspace monorepo with `frontend/`, `backend/`, and `packages/shared/`.
* Initialize a new Astro project configured for SSR inside `frontend/`.
* Set up Payload CMS for Cloudflare Workers inside `backend/`.
* Configure Tailwind CSS and shared TypeScript utilities in `packages/shared/`.
2. **Phase 2: Authentication & CMS Setup**
* Integrate `astro-auth` and configure the login flow.
* Define the collections and user roles (`admin`, `editor`) within Payload.