Submitting, Maintaining and Growing a Plugin on WordPress.org
summary
Requires a readme.txt with validated header and matching version numbers, and all bundled files (PHP, JS, CSS, images) must be GPL for all assets and readable; use WP_DEBUG and console checks, avoid bundling a custom jQuery, and limit tags (~12). Submit a zip to plugins.add then get an SVN repo and follow the SVN trunk/tags workflow (commit only releases), add assets/screenshots in the assets folder, don’t track installs or add front‑end credits without consent, and plan updates ~every six months.
AI-written summary · about
chapters (12)
- 0:00Start
- 4:43Screenshots
- 6:00Validation Tool
- 6:30Gpl License
- 13:02Release Your Plugin
- 13:52Test with Wp Underscore Debug
- 17:38Svn Repository
- 19:16Add Screenshots Icon Header Images
- 24:24Tips
- 27:58Add a Plugin Help Page
- 31:04Frequent Updates
- 32:57Any Recommendations for the Support Requests That Come in and How To Handle Them
