The document discusses 10 ways to build a developer-friendly WordPress plugin, including using GitHub/GitLab for issue tracking and pull requests, adding hooks for actions and filters, following coding standards, using object-oriented programming principles, enabling translations, unit testing, providing get_by methods, deprecating old methods, and following semantic versioning. The overall goal is to contribute high quality, well-supported plugins to the WordPress ecosystem.

1. @mikehale#wcchi
Building a Developer
Friendly WordPress Plugin
WordCamp Chicago 2017

2. Why?

5. Contribute to WordPress

6. Futureproof Code

7. Support Requests

8. Ratings & Reviews

9. 10 Ways to Build a
Developer Friendly
WordPress Plugin

10. 1. GitHub / GitLab
Issue Management
Pull Requests

12. 2. Add Hooks
Actions Filters

13. Actions
Run code at a specific time or event
add_action()
do_action()

14. Filters
Modify data being returned
add_filter()
apply_filters()

16. 3. Coding Standards
WordPress PHP Coding Standards
Plugin Handbook
PHPDocs
PHPCS (Code sniffer)
PHP PSR-x Standards

17. WordPress Standards

18. Plugin Handbook

19. PHPDocs

20. Code Sniffer (PHPCS)

21. 4. OOP
Extends
Implements
Abstracts
Avoid method name collisions
Organization and Reuse

22. 5. Develop with Debug

23. 6. Translations (18n)
.po & .pot files

24. 7. Unit Testing

25. 8. get_by
… with a little help from my friends.
ID, Title, Slug, Meta

28. 9. Deprecate Methods
_deprecated_function()
Bump Minor Version

29. 10. Semantic Versioning
Major.Minor.Patch (4.7.2)

30. Major Version
Major or Breaking
Changes

31. Minor Version
New Functionality
(Backwards Compatible)

32. Patch Version
Bug Fixes
(Backwards Compatible)

33. Recap
● GitHub/Gitlab
● Add Actions and Filters
● Coding standards
● OOP
● Develop with Debug
● Make it Translatable
● Unit Testing
● get_by methods
● Deprecate methods
● Semantic Versioning

34. About Me
Mike Hale
Developer
Rainmaker Digital
@MikeHale
www.mikehale.me