Designing Plugins for Release
•Download as PPTX, PDF•
0 likes•1,048 views
Releasing plugins on the WordPress repository is hard. Here is a quick checklist of things to look out for.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (14)
Similar to Designing Plugins for Release
Similar to Designing Plugins for Release (20)
Recently uploaded
Recently uploaded (20)
Designing Plugins for Release
- 1. WordCamp DFW 2015 - #WCDFW Designing Plugins for Release by Ronald Huereca - @ronalfy
- 2. @ronalfy This Presentation Will Not Teach You How to Code Sorry :(
- 3. @ronalfy Let’s make this 80,000! Just don’t tell the plugin team I said that
- 4. @ronalfy 0. Find a Plugin
- 5. @ronalfy Places of Inspiration • Your client projects • Your internal WordPress frustrations • Contributing or adding to an existing project • Taking over an existing project • Social Media • Support Forums • Ask a friend
- 6. @ronalfy adopt-me tag De-factor WordPress Plugin Adoption Headquarters
- 7. @ronalfy 1. Choose where development happens
- 8. @ronalfy 2. Decide up-front on your release model
- 9. @ronalfy 3. Build your plugin to be flexible
- 10. @ronalfy –Andrew Nacin “Many WordPress plugins subject their users to too many options. Don’t add settings screens simply because you know how. Challenge yourself. Learn to decide.”
- 11. @ronalfy 4. Take your code. Clean it up. Then clean it up again.
- 12. @ronalfy Quick Coding Tips • Adhere to standards • Code with debug mode on • Scripts should adhere to SCRIPT_DEBUG (minified if off, uncompressed if on)
- 13. @ronalfy 5. Gather your assets
- 17. @ronalfy 6. Prepare to be translated
- 25. @ronalfy –Me “Do not release a plugin if you have no intention of supporting it.”
- 29. @ronalfy .org responsibilities • Don’t phone home • Don’t spam • Don’t do anything malicious • Don’t copy • Keep up-to-date (in an ideal world)
- 32. @ronalfy Questions? ease tweet me any questions and I’ll try my best to answer the slideshare / ronalfy
Editor's Notes
- Designing a release is preparing your plugin for mass consumption. It is an art form.
- Everybody has their own style, workflow, etc. No classes, namespaces, autoloaders, grunt, vvv, etc.
- A bit of code you would like to see made into a full plugin Taking over someone else’s plugin Initial or preview release for a premium plugin model
- Example: new designer at my work asked if he can help contribute to an Open Source project.
- https://wordpress.org/plugins/tags/adopt-me
- Only on SVN GitHub Other?
- Free forever? Core + add-ons? Puzzle/Jigsaw/in-app-purchase model Paid forever
- Use actions/filters Add an options panel Decisions, not options
- Source: https://nacin.com/2011/12/18/in-open-source-learn-to-decide/
- Follow WordPress coding standards Proper indentation (tabs, spaces, eh) Incline documentation
- https://make.wordpress.org/core/handbook/best-practices/coding-standards/php/
- Screenshots, plugin header, plugin header https://wordpress.org/plugins/about/faq/
- Place in SVN /assets banner-772x250.png banner-1544x500.png
- Place in SVN /assets icon-128x128.png icon-256x256.png
- Make your plugin internationalization ready Built POT files (soon to be a thing of the past) Set up translation on poeditor.com or something similar (soon to be a thing of the past)
- Written, video, animated gif, readme.md, readme.txt, faq, changelog
- User testing Sanity testing Test your filters and extensibility Unit Testing (https://pippinsplugins.com/unit-tests-wordpress-plugins-introduction/)
- Monitor for common bugs, questions, and feature requests. Too many questions means your documentation needs updating