mirror of
https://github.com/PanJiaChen/vue-element-admin.git
synced 2025-08-07 18:25:45 +08:00
Add files via upload
This commit is contained in:
parent
6858a9ad67
commit
64a32cf79a
278
AGENTS.md
Normal file
278
AGENTS.md
Normal file
@ -0,0 +1,278 @@
|
|||||||
|
I'll help you create comprehensive descriptions, tasks, and user stories for your centralized WordPress management dashboard project. Let me draft a GitHub issue with all the necessary details.
|
||||||
|
|
||||||
|
<github-draft-issue>
|
||||||
|
# Centralized WordPress Management Dashboard with Google Ad Manager Integration
|
||||||
|
|
||||||
|
## Project Overview
|
||||||
|
|
||||||
|
Build a full-stack centralized control panel dashboard to manage a large number of WordPress sites with integrated Google Ad Manager reporting. The system will provide comprehensive site management capabilities and role-based access control.
|
||||||
|
|
||||||
|
## Core Features
|
||||||
|
|
||||||
|
### 1. **Multi-Site WordPress Management**
|
||||||
|
- Centralized control for multiple WordPress installations
|
||||||
|
- Integration with WordPress Multisite architecture
|
||||||
|
- Real-time site status monitoring
|
||||||
|
- Bulk operations across multiple sites
|
||||||
|
|
||||||
|
### 2. **Role-Based Access Control**
|
||||||
|
- **Admin Role**: Full system control including all sites, settings, and configurations
|
||||||
|
- **Publisher Role**: Content-specific privileges (create, edit, publish content)
|
||||||
|
- Granular permission management
|
||||||
|
- User activity logging and audit trails
|
||||||
|
|
||||||
|
### 3. **Google Ad Manager Integration**
|
||||||
|
- Direct integration with Google Ad Manager accounts
|
||||||
|
- Real-time AdX report pulling and visualization
|
||||||
|
- Site-specific revenue tracking
|
||||||
|
- Customizable report filters matching WP Multisite structure
|
||||||
|
|
||||||
|
### 4. **Content Management**
|
||||||
|
- Cross-site content review and approval workflows
|
||||||
|
- Bulk content operations
|
||||||
|
- Content scheduling across multiple sites
|
||||||
|
- Media library management
|
||||||
|
|
||||||
|
### 5. **Plugin/Theme Management**
|
||||||
|
- Centralized plugin installation and updates
|
||||||
|
- Theme management across all sites
|
||||||
|
- Compatibility checking
|
||||||
|
- Automated backup before updates
|
||||||
|
|
||||||
|
## User Stories
|
||||||
|
|
||||||
|
### Epic 1: Authentication & Authorization
|
||||||
|
```
|
||||||
|
As an administrator
|
||||||
|
I want to have secure login with role-based access
|
||||||
|
So that I can manage user permissions effectively
|
||||||
|
```
|
||||||
|
|
||||||
|
**Acceptance Criteria:**
|
||||||
|
- Secure authentication system implemented
|
||||||
|
- Two distinct roles (Admin/Publisher) with different permission sets
|
||||||
|
- Session management and timeout features
|
||||||
|
- Password reset functionality
|
||||||
|
|
||||||
|
### Epic 2: Dashboard Overview
|
||||||
|
```
|
||||||
|
As a dashboard user
|
||||||
|
I want to see an overview of all WordPress sites at a glance
|
||||||
|
So that I can quickly assess the status of my network
|
||||||
|
```
|
||||||
|
|
||||||
|
**Acceptance Criteria:**
|
||||||
|
- Grid/list view of all managed WordPress sites
|
||||||
|
- Real-time status indicators (online/offline, last update, etc.)
|
||||||
|
- Quick stats (posts, pages, users per site)
|
||||||
|
- Search and filter functionality
|
||||||
|
|
||||||
|
### Epic 3: WordPress Site Management
|
||||||
|
```
|
||||||
|
As an administrator
|
||||||
|
I want to manage multiple WordPress sites from one interface
|
||||||
|
So that I can efficiently maintain all sites without logging into each one
|
||||||
|
```
|
||||||
|
|
||||||
|
**Acceptance Criteria:**
|
||||||
|
- Add/remove WordPress sites to the dashboard
|
||||||
|
- Update WordPress core, themes, and plugins across sites
|
||||||
|
- Manage site settings remotely
|
||||||
|
- Backup and restore functionality
|
||||||
|
|
||||||
|
### Epic 4: Content Management
|
||||||
|
```
|
||||||
|
As a publisher
|
||||||
|
I want to create and manage content across multiple sites
|
||||||
|
So that I can efficiently publish content without switching between sites
|
||||||
|
```
|
||||||
|
|
||||||
|
**Acceptance Criteria:**
|
||||||
|
- Create/edit posts and pages for any managed site
|
||||||
|
- Bulk content operations
|
||||||
|
- Content preview before publishing
|
||||||
|
- Media upload and management
|
||||||
|
|
||||||
|
### Epic 5: Google Ad Manager Integration
|
||||||
|
```
|
||||||
|
As an administrator
|
||||||
|
I want to view AdX reports for all my WordPress sites
|
||||||
|
So that I can monitor revenue performance in one place
|
||||||
|
```
|
||||||
|
|
||||||
|
**Acceptance Criteria:**
|
||||||
|
- Connect Google Ad Manager account
|
||||||
|
- Pull real-time AdX reports
|
||||||
|
- Filter reports by site (matching WP Multisite structure)
|
||||||
|
- Export reports in multiple formats
|
||||||
|
|
||||||
|
## Technical Tasks
|
||||||
|
|
||||||
|
### Phase 1: Foundation (Weeks 1-3)
|
||||||
|
|
||||||
|
#### Backend Setup
|
||||||
|
- [ ] Set up Node.js/Express server with TypeScript
|
||||||
|
- [ ] Configure database (PostgreSQL/MongoDB) for dashboard data
|
||||||
|
- [ ] Implement authentication system (JWT)
|
||||||
|
- [ ] Create role-based middleware
|
||||||
|
- [ ] Set up API documentation (Swagger/OpenAPI)
|
||||||
|
|
||||||
|
#### Frontend Setup
|
||||||
|
- [ ] Initialize React/Next.js application with TypeScript
|
||||||
|
- [ ] Set up state management (Redux/Zustand)
|
||||||
|
- [ ] Configure routing and navigation
|
||||||
|
- [ ] Implement responsive design system
|
||||||
|
- [ ] Set up component library (MUI/Ant Design)
|
||||||
|
|
||||||
|
### Phase 2: WordPress Integration (Weeks 4-6)
|
||||||
|
|
||||||
|
#### WordPress API Integration
|
||||||
|
- [ ] Implement WordPress REST API client
|
||||||
|
- [ ] Create service for WordPress Multisite communication
|
||||||
|
- [ ] Build site discovery mechanism
|
||||||
|
- [ ] Implement secure API key management
|
||||||
|
- [ ] Create WordPress webhook receivers
|
||||||
|
|
||||||
|
#### Site Management Features
|
||||||
|
- [ ] Build site listing and filtering UI
|
||||||
|
- [ ] Implement site health monitoring
|
||||||
|
- [ ] Create plugin/theme management interface
|
||||||
|
- [ ] Build bulk update functionality
|
||||||
|
- [ ] Implement backup/restore features
|
||||||
|
|
||||||
|
### Phase 3: Content Management (Weeks 7-8)
|
||||||
|
|
||||||
|
#### Content Operations
|
||||||
|
- [ ] Create unified content editor
|
||||||
|
- [ ] Implement cross-site content search
|
||||||
|
- [ ] Build media library integration
|
||||||
|
- [ ] Create content scheduling system
|
||||||
|
- [ ] Implement revision history
|
||||||
|
|
||||||
|
#### Publisher Features
|
||||||
|
- [ ] Build publisher dashboard
|
||||||
|
- [ ] Create content approval workflow
|
||||||
|
- [ ] Implement content templates
|
||||||
|
- [ ] Build SEO optimization tools
|
||||||
|
|
||||||
|
### Phase 4: Google Ad Manager Integration (Weeks 9-10)
|
||||||
|
|
||||||
|
#### AdX Integration
|
||||||
|
- [ ] Implement Google Ad Manager API client
|
||||||
|
- [ ] Create OAuth2 flow for Google authentication
|
||||||
|
- [ ] Build report pulling service
|
||||||
|
- [ ] Create report caching mechanism
|
||||||
|
- [ ] Implement real-time data sync
|
||||||
|
|
||||||
|
#### Reporting Dashboard
|
||||||
|
- [ ] Design report visualization components
|
||||||
|
- [ ] Create customizable report filters
|
||||||
|
- [ ] Build report export functionality
|
||||||
|
- [ ] Implement scheduled report generation
|
||||||
|
- [ ] Create revenue analytics dashboard
|
||||||
|
|
||||||
|
### Phase 5: Advanced Features (Weeks 11-12)
|
||||||
|
|
||||||
|
#### System Features
|
||||||
|
- [ ] Implement activity logging
|
||||||
|
- [ ] Create notification system
|
||||||
|
- [ ] Build API rate limiting
|
||||||
|
- [ ] Implement data encryption
|
||||||
|
- [ ] Create system backup functionality
|
||||||
|
|
||||||
|
#### Performance & Security
|
||||||
|
- [ ] Implement caching strategies
|
||||||
|
- [ ] Add CDN integration
|
||||||
|
- [ ] Create security scanning features
|
||||||
|
- [ ] Build performance monitoring
|
||||||
|
- [ ] Implement automated testing
|
||||||
|
|
||||||
|
## Technical Specifications
|
||||||
|
|
||||||
|
### Technology Stack
|
||||||
|
- **Backend**: Node.js, Express.js, TypeScript
|
||||||
|
- **Frontend**: React/Next.js, TypeScript, TailwindCSS
|
||||||
|
- **Database**: PostgreSQL for relational data, Redis for caching
|
||||||
|
- **Authentication**: JWT with refresh tokens
|
||||||
|
- **APIs**: WordPress REST API, Google Ad Manager API
|
||||||
|
- **Deployment**: Docker, Kubernetes
|
||||||
|
|
||||||
|
### API Endpoints Structure
|
||||||
|
```
|
||||||
|
/api/v1/auth/* - Authentication endpoints
|
||||||
|
/api/v1/sites/* - WordPress site management
|
||||||
|
/api/v1/content/* - Content management
|
||||||
|
/api/v1/reports/* - AdX reporting
|
||||||
|
/api/v1/users/* - User management
|
||||||
|
/api/v1/settings/* - System settings
|
||||||
|
```
|
||||||
|
|
||||||
|
### Database Schema Considerations
|
||||||
|
- Users table with role assignments
|
||||||
|
- Sites table with WordPress connection details
|
||||||
|
- Content tracking table
|
||||||
|
- Reports cache table
|
||||||
|
- Activity logs table
|
||||||
|
- Settings and configurations
|
||||||
|
|
||||||
|
## Security Requirements
|
||||||
|
- Encrypted storage of WordPress credentials
|
||||||
|
- Secure API key management
|
||||||
|
- Rate limiting on all endpoints
|
||||||
|
- Input validation and sanitization
|
||||||
|
- Regular security audits
|
||||||
|
- GDPR compliance features
|
||||||
|
|
||||||
|
## Performance Requirements
|
||||||
|
- Dashboard load time < 2 seconds
|
||||||
|
- Real-time updates via WebSockets
|
||||||
|
- Support for 1000+ WordPress sites
|
||||||
|
- Concurrent user support (100+ users)
|
||||||
|
- 99.9% uptime SLA
|
||||||
|
|
||||||
|
## Testing Strategy
|
||||||
|
- Unit tests for all business logic
|
||||||
|
- Integration tests for API endpoints
|
||||||
|
- E2E tests for critical user flows
|
||||||
|
- Performance testing for scalability
|
||||||
|
- Security penetration testing
|
||||||
|
|
||||||
|
## Deployment & DevOps
|
||||||
|
- CI/CD pipeline setup
|
||||||
|
- Container orchestration
|
||||||
|
- Monitoring and alerting
|
||||||
|
- Backup and disaster recovery
|
||||||
|
- Documentation and runbooks
|
||||||
|
|
||||||
|
## Success Metrics
|
||||||
|
- Reduction in site management time by 80%
|
||||||
|
- Single dashboard for all operations
|
||||||
|
- Real-time visibility into AdX performance
|
||||||
|
- Improved content publishing efficiency
|
||||||
|
- Reduced security incidents
|
||||||
|
|
||||||
|
## Dependencies
|
||||||
|
- WordPress Multisite installation
|
||||||
|
- Google Ad Manager account with API access
|
||||||
|
- Hosting infrastructure
|
||||||
|
- SSL certificates
|
||||||
|
- Domain configuration
|
||||||
|
</github-draft-issue>
|
||||||
|
|
||||||
|
I've created a comprehensive GitHub issue draft that includes:
|
||||||
|
|
||||||
|
1. **Detailed Project Overview** - Explaining the centralized dashboard concept
|
||||||
|
2. **Core Features** - Breaking down the main functionalities
|
||||||
|
3. **User Stories** - Following Agile methodology with clear acceptance criteria
|
||||||
|
4. **Technical Tasks** - Organized in phases with specific implementation items
|
||||||
|
5. **Technical Specifications** - Including tech stack and architecture details
|
||||||
|
6. **Additional Requirements** - Security, performance, testing, and deployment considerations
|
||||||
|
|
||||||
|
The structure follows a typical software development project format with:
|
||||||
|
- Clear feature descriptions
|
||||||
|
- Role-based access control specifications (Admin vs Publisher)
|
||||||
|
- WordPress Multisite integration details
|
||||||
|
- Google Ad Manager integration requirements
|
||||||
|
- Comprehensive task breakdown for implementation
|
||||||
|
|
||||||
|
This can be used as a master issue or epic, with individual tasks being created as separate issues for better project management. Would you like me to create additional, more specific issues for any particular component or phase of the project?
|
Loading…
x
Reference in New Issue
Block a user