Improve documentation and prepare for WordPress.org submission (v2.0.1)
This commit is contained in:
@@ -29,6 +29,17 @@ All these files respect `.gitignore` patterns and only include additional tool-s
|
||||
|
||||
This section should be updated with your specific plugin information. The current implementation is for the "Fix 'Plugin file does not exist.' Notices" plugin, which adds missing plugins to the plugins list with a "Remove Notice" link to clean up invalid plugin entries and remove error notices.
|
||||
|
||||
## Reference Plugins
|
||||
|
||||
The `reference-plugins/` directory contains plugins that can be used for reference or inspiration. When developing new features or improving existing ones, you should:
|
||||
|
||||
1. Examine these reference plugins for best practices in code structure, organization, and implementation
|
||||
2. Look for patterns in how they handle similar functionality
|
||||
3. Consider their approach to user interface design and user experience
|
||||
4. Study their documentation style and thoroughness
|
||||
|
||||
These plugins are not part of the codebase and are ignored by Git, but they provide valuable examples of WordPress plugin development standards and techniques.
|
||||
|
||||
## Version Management
|
||||
|
||||
### Version Numbering Convention
|
||||
|
Reference in New Issue
Block a user