pkupuk
f6b806617e
Include supplementary documentation, research notes on Lexical/UX, and setup guides.
138 lines
5.3 KiB
Markdown
138 lines
5.3 KiB
Markdown
# 1. Project Analysis and Context
|
||
|
||
**Last Updated:** 2025-01-29
|
||
|
||
## Existing Project Overview
|
||
|
||
### Analysis Source
|
||
- **Type:** IDE-based fresh analysis
|
||
- **Research Materials:** `research/www.enchun.tw/` directory
|
||
|
||
### Current Project State
|
||
|
||
#### Original System (Webflow)
|
||
**Platform:** Webflow CMS + Hosted Website
|
||
**Website:** www.enchun.tw (恩群數位行銷)
|
||
**Purpose:** Corporate showcase website + content marketing platform
|
||
**Content Structure:**
|
||
- 7 main pages
|
||
- 4 article categories
|
||
- 35+ blog articles
|
||
- Portfolio showcase
|
||
- Team profiles
|
||
|
||
**Target Audience:**
|
||
- Potential clients (seeking digital marketing services)
|
||
- Internal editors (content management)
|
||
- Administrators (system management)
|
||
|
||
#### Target System (New Architecture)
|
||
**Architecture:** Monorepo (pnpm workspaces)
|
||
```
|
||
website-enchun-mgr/
|
||
├── apps/
|
||
│ ├── backend/ # Payload CMS (Headless CMS)
|
||
│ └── frontend/ # Astro (SSR frontend)
|
||
└── packages/
|
||
└── shared/ # Shared TypeScript utilities
|
||
```
|
||
|
||
**Technology Stack:**
|
||
- **Frontend:** Astro 6.0.x (SSR mode + Cloudflare native runtime) + Tailwind CSS v4 + TypeScript
|
||
- **Backend/CMS:** Payload CMS 3.x + MongoDB
|
||
- **Authentication:** Payload CMS built-in authentication system ✅
|
||
- **Deployment:** Cloudflare Pages (frontend) + Node.js (Payload CMS admin)
|
||
- **Storage:** Cloudflare R2 (media files)
|
||
|
||
**為什麼選擇 Astro 6.0？**
|
||
- ✅ Cloudflare native runtime - 開發和生產使用相同環境
|
||
- ✅ 原生 Cloudflare Workers 整合（Cloudflare 2026年1月收購 Astro）
|
||
- ✅ 支援 Rate Limiting、PDF Generation、Live Collaborative Editing
|
||
- ✅ 更快的 Cloudflare Pages 部署和邊緣快取
|
||
|
||
### Migration Drivers
|
||
|
||
1. **Performance Improvement:** Target Lighthouse 95+ scores
|
||
2. **Cost Optimization:** Reduce Webflow subscription fees
|
||
3. **Flexibility:** Greater customization capabilities and integration options
|
||
4. **Maintainability:** Modern development toolchain and better DX
|
||
5. **SEO Preservation:** Maintain and improve existing SEO value
|
||
|
||
---
|
||
|
||
## Available Documentation Analysis
|
||
|
||
### Available Documentation
|
||
|
||
| Document | Status | Notes |
|
||
|----------|--------|-------|
|
||
| Tech Stack Documentation | ❌ Needs creation | |
|
||
| Source Tree/Architecture | ❌ Needs creation | |
|
||
| Coding Standards | ❌ Needs creation | |
|
||
| API Documentation | ❌ Needs creation | |
|
||
| UX/UI Guidelines | ❌ Needs extraction from Webflow | |
|
||
| CMS Collection Structure | ✅ Available | `cms_structure.md` |
|
||
| Original PRD | ✅ Available | `PRD.md` (high-level needs) |
|
||
|
||
### Recommendation
|
||
|
||
**Action Required:** Run `document-project` task before implementation to establish:
|
||
- Complete technical documentation
|
||
- Architecture diagrams
|
||
- Coding standards
|
||
- API specifications
|
||
|
||
This will help the development team better understand existing patterns and constraints.
|
||
|
||
---
|
||
|
||
## Enhancement Scope Definition
|
||
|
||
### Enhancement Type
|
||
✅ **Technology Stack Migration** (Complete platform migration)
|
||
|
||
### Enhancement Description
|
||
|
||
Migrate the existing Webflow CMS-hosted website completely to a modernized Payload CMS + Astro architecture while maintaining all content, SEO value, and user experience. This includes page reconstruction, content migration, SEO redirects, authentication system implementation, and CMS admin interface integration.
|
||
|
||
### Impact Assessment
|
||
✅ **Major Impact** (Architectural changes required)
|
||
- Complete frontend framework replacement
|
||
- Migration from hosted CMS to self-hosted Headless CMS
|
||
- New authentication and authorization system
|
||
- Data migration and structure transformation
|
||
|
||
---
|
||
|
||
## Goals and Background Context
|
||
|
||
### Goals
|
||
|
||
1. ✅ Fully migrate all 7 main pages with 95%+ visual fidelity to original design
|
||
2. ✅ Migrate 35+ blog articles and 4 categories to Payload CMS
|
||
3. ✅ Implement complete 301 redirect mappings to preserve SEO equity
|
||
4. ✅ Achieve Lighthouse performance scores of 95+ for all public pages
|
||
5. ✅ Establish secure authentication system supporting Admin and Editor roles
|
||
6. ✅ Build user-friendly CMS admin interface for content editors
|
||
7. ✅ Deploy to Cloudflare Pages + Workers infrastructure
|
||
8. ✅ Maintain or improve existing SEO rankings and organic traffic
|
||
|
||
### Background Context
|
||
|
||
Enchun Digital Marketing currently uses Webflow CMS for their corporate website and content marketing platform. While Webflow provides convenient visual editing and hosting, long-term costs and technical limitations have become growth bottlenecks. To achieve better cost-effectiveness, greater customization flexibility, and modernized development and deployment workflows, the company has decided to migrate to a Payload CMS + Astro architecture.
|
||
|
||
This migration is not just a technology platform switch, but aims to establish a scalable, high-performance, and maintainable digital platform to support Enchun Digital's long-term business growth. The migration process must ensure content integrity, SEO value preservation, and user experience continuity.
|
||
|
||
---
|
||
|
||
## Change Log
|
||
|
||
| Change | Date | Version | Description | Author |
|
||
|--------|------|---------|-------------|--------|
|
||
| Initial creation | 2025-01-29 | v4 | Brownfield PRD created from migration analysis | PM Agent |
|
||
| Authentication correction | 2025-01-29 | v4.1 | Corrected Auth.js references to Payload CMS built-in auth | PM Agent |
|
||
|
||
---
|
||
|
||
**Next Section:** [Requirements](./02-requirements.md)
|