designing plugins for release
TRANSCRIPT
WordCamp DFW 2015 - #WCDFW
Designing Plugins for Release
by Ronald Huereca - @ronalfy
@ronalfy
This Presentation Will Not Teach You How to
CodeSorry :(
@ronalfy
Let’s make this 80,000!Just don’t tell the plugin team I said that
@ronalfy
0. Find a Plugin
@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
@ronalfy
adopt-me tagDe-factor WordPress Plugin Adoption Headquarters
@ronalfy
1. Choose where development happens
@ronalfy
2. Decide up-front on your release model
@ronalfy
3. Build your plugin to be flexible
@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.”
@ronalfy
4. Take your code. Clean it up. Then clean it up
again.
@ronalfy
Quick Coding Tips
• Adhere to standards
• Code with debug mode on
• Scripts should adhere to SCRIPT_DEBUG (minified if off, uncompressed if on)
@ronalfy
5. Gather your assets
@ronalfy
Plugin Banner
@ronalfy
Plugin Screenshots
@ronalfy
Plugin Icons
@ronalfy
6. Prepare to be translated
@ronalfy
7. Documentation
@ronalfy
Readme Docs
@ronalfy
Video/Gif
@ronalfy
FAQ Section
@ronalfy
Changelog
@ronalfy
8. Testing
@ronalfy
9. Support
@ronalfy
–Me
“Do not release a plugin if you have no intention of supporting it.”
@ronalfy
Subscribe to Emails
@ronalfy
Provide Good Support
@ronalfy
Ask for Ratings
@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)
@ronalfy
–Others
“Be nice.”
@ronalfy
–Me
“Be superhero nice.”
@ronalfy
Questions?Please tweet me any questions and I’ll try my best to answer them.
slideshare / ronalfy