138 lines
7.0 KiB
Markdown
138 lines
7.0 KiB
Markdown
# WP Allstars Plugin Development Roadmap
|
|
|
|
This document outlines features from later versions that we plan to integrate into our stable development branch. The goal is to incrementally implement these features in a stable manner, without introducing critical errors.
|
|
|
|
## Feature Backlog
|
|
|
|
| Feature | Source Version | Priority | Complexity | Risk | Status |
|
|
|---------|----------------|----------|------------|------|--------|
|
|
| Multisite Category | v0.2.6 | High | Low | Low | ✅ Implemented in v0.2.3-stable |
|
|
| Sync Guard | v0.2.6-fix | High | Low | Low | ✅ Implemented in v0.2.3.1-stable |
|
|
| More Robust File Loading | v0.2.6-fix | High | Low | Low | ✅ Implemented in v0.2.3-stable |
|
|
| Admin Colors Feature | v0.2.4 | High | Low | Low | 🔄 To be implemented |
|
|
| Basic Admin UI Enhancements | v0.2.5 | High | Medium | Medium | 🔄 To be implemented |
|
|
| Advanced Admin UI Components | v0.2.5 | Medium | Medium | Medium | 🔄 To be implemented |
|
|
| Access Manager Improvements | v0.2.5 | Medium | Medium | Medium | 🔄 To be implemented |
|
|
| Role-Based Access Controls | v0.2.5.1 | High | Medium | Medium | 🔄 To be implemented |
|
|
| Improved Plugin Structure | v0.2.5 | Medium | Medium | High | 🔄 To be implemented |
|
|
| Performance Optimizations | v0.2.6 | Medium | Medium | Medium | 🔄 To be implemented |
|
|
| Enhanced Plugin Filtering | v0.2.6 | Medium | Medium | Low | 🔄 To be implemented |
|
|
| Plugin Settings Export/Import | v0.2.6 | Low | High | Medium | 🔄 To be implemented |
|
|
| Plugin Dashboard | v0.2.6-fix | Medium | Medium | Medium | 🔄 To be implemented |
|
|
| New Category Pages | v0.2.4+ | Medium | Low | Low | 🔄 To be implemented |
|
|
|
|
## Implementation Strategy
|
|
|
|
### Multisite Category with Network Plugin Auditor
|
|
- **Description**: Add a "Multisite" filter after Advanced and include network-plugin-auditor
|
|
- **Why it failed before**: Didn't properly update all required files for the feature
|
|
- **Implementation plan**: Add to free-plugins.php and update class-free-plugins-manager.php to display the category correctly
|
|
- **Testing criteria**: Verify category appears in UI and plugin can be installed
|
|
|
|
### Sync Guard
|
|
- **Description**: Prevent plugin loading during rsync operations to avoid partial file loading
|
|
- **Why it failed before**: Added to wrong location, dependent on missing files
|
|
- **Implementation plan**:
|
|
1. Create a simpler version of the sync guard
|
|
2. Update post-commit hook to handle sync operations better
|
|
3. Use file flag to signal when sync is in progress
|
|
- **Testing criteria**: Verify plugin doesn't attempt to load during sync operations
|
|
|
|
### Admin Colors Feature
|
|
- **Description**: Allow users to switch between default and modern admin color schemes
|
|
- **Why it's valuable**: Provides visual distinction and improves user experience
|
|
- **Implementation plan**:
|
|
1. Create class-wp-allstars-admin-colors.php
|
|
2. Add toggle in settings to switch color schemes
|
|
3. Register the feature in the main plugin file
|
|
- **Testing criteria**: Verify color scheme changes when toggled
|
|
|
|
### Basic Admin UI Enhancements
|
|
- **Description**: Improve the basic styling of admin interfaces
|
|
- **Why it's valuable**: Better user experience and modern look
|
|
- **Implementation plan**:
|
|
1. Create/update wp-allstars-admin.css
|
|
2. Implement basic styling for cards, panels, and buttons
|
|
3. Add responsive design improvements
|
|
- **Testing criteria**: Verify UI looks consistent across different screen sizes
|
|
|
|
### Advanced Admin UI Components
|
|
- **Description**: Add more sophisticated UI elements and interactions
|
|
- **Why it's valuable**: Enhanced usability and professional appearance
|
|
- **Implementation plan**:
|
|
1. Implement enhanced toggles and accordions
|
|
2. Add notification styling
|
|
3. Improve plugin cards and layouts
|
|
- **Testing criteria**: Verify all UI components work correctly across browsers
|
|
|
|
### Access Manager Improvements
|
|
- **Description**: Enhance user role and permission management
|
|
- **Why it's valuable**: More granular control over plugin features
|
|
- **Implementation plan**:
|
|
1. Update class-access-manager.php
|
|
2. Add role checkboxes in UI
|
|
3. Implement proper access restriction handling
|
|
- **Testing criteria**: Verify correct permissions are applied based on user roles
|
|
|
|
### Role-Based Access Controls
|
|
- **Description**: Implement fine-grained access controls for different user roles
|
|
- **Why it's valuable**: Allows administrators to restrict access to specific plugin features
|
|
- **Implementation plan**:
|
|
1. Create role capability mapping system
|
|
2. Add permission checks throughout the plugin
|
|
3. Create UI for managing role permissions
|
|
- **Testing criteria**: Verify users can only access features appropriate to their role
|
|
|
|
### Improved Plugin Structure
|
|
- **Description**: Better organization of code with clearer separation of concerns
|
|
- **Why it's valuable**: More maintainable codebase and fewer dependency issues
|
|
- **Implementation plan**:
|
|
1. Reorganize class loading order
|
|
2. Improve dependency management
|
|
3. Enhance error handling for API calls
|
|
- **Testing criteria**: Verify plugin loads correctly with no dependency errors
|
|
|
|
### Performance Optimizations
|
|
- **Description**: Improve plugin performance and resource usage
|
|
- **Why it's valuable**: Better user experience and lower server load
|
|
- **Implementation plan**:
|
|
1. Optimize asset loading (CSS/JS)
|
|
2. Reduce database queries
|
|
3. Implement caching for external API requests
|
|
- **Testing criteria**: Verify reduced page load times and server resource usage
|
|
|
|
### Enhanced Plugin Filtering
|
|
- **Description**: More advanced filtering options for the plugins section
|
|
- **Why it's valuable**: Makes it easier for users to find relevant plugins
|
|
- **Implementation plan**:
|
|
1. Add category-specific icons and metadata
|
|
2. Implement more filtering options
|
|
3. Improve search functionality
|
|
- **Testing criteria**: Verify filtering works correctly and improves plugin discovery
|
|
|
|
### Plugin Settings Export/Import
|
|
- **Description**: Allow users to backup and restore plugin settings
|
|
- **Why it's valuable**: Easier migration between environments and configuration backup
|
|
- **Implementation plan**:
|
|
1. Create export functionality for settings
|
|
2. Implement import/restore capability
|
|
3. Add settings profiles for different use cases
|
|
- **Testing criteria**: Verify settings can be exported and successfully imported on another site
|
|
|
|
## Development Order
|
|
|
|
The suggested implementation order is:
|
|
|
|
1. Admin Colors Feature (low complexity, enhances UI)
|
|
2. Basic Admin UI Enhancements (foundation for other UI improvements)
|
|
3. Role-Based Access Controls (security-related, high priority)
|
|
4. Advanced Admin UI Components (builds on basic UI)
|
|
5. Access Manager Improvements (depends on UI components and role controls)
|
|
6. Performance Optimizations (improves user experience)
|
|
7. Enhanced Plugin Filtering (better usability)
|
|
8. Improved Plugin Structure (code quality)
|
|
9. Plugin Dashboard improvements (adds functionality)
|
|
10. New Category Pages (content enhancement)
|
|
11. Plugin Settings Export/Import (advanced functionality)
|
|
|
|
Each feature should be developed in its own branch and only merged after thorough testing. |