The document is a presentation on WordPress plugin development by Joey Kudish, detailing the purpose and functionality of plugins, including action and filter hooks. It provides insights on coding standards, security measures, and resources for further learning. The presentation includes demos and emphasizes using built-in APIs and being courteous to other developers.

1. Plugin
Development
- Joey Kudish
http://slides.jkudish.com
Friday, 11 January, 13

2. About me
• WordPress developer since 2007
• Initially built sites for a variety of clients
• Freelance plugin development
• Code Wrangler at WordPress.com / Automattic
since May 2011
• Originally from Montreal, moved to Vancouver
in 2011
Friday, 11 January, 13

3. Friday, 11 January, 13

4. What’s a
plugin?
Friday, 11 January, 13

5. A plugin extends or
modi!es WordPress
to do something it
didn’t previously do
Friday, 11 January, 13

6. Themes can act as
plugins. Oh and there’s
mu-plugins too.
Friday, 11 January, 13

7. Plugins can be
huge...
Friday, 11 January, 13

8. ... or tiny.
Friday, 11 January, 13

9. What’s in a plugin?
Friday, 11 January, 13

10. Where does it
go?
wp-content/plugins/[plugin_name]
or wp-content/mu-plugins/
Friday, 11 January, 13

11. In order to “hook”
into WordPress, we
use action and !lter
hooks
Friday, 11 January, 13

12. Action hooks allow
you to add your own
code to WordPress’
call stack
Friday, 11 January, 13

13. Filter hooks allow
you to modify an
existing variable or
piece of information
Friday, 11 January, 13

14. Demo time
Friday, 11 January, 13

15. Let’s add Google
Webmaster Tools
veri!cation to our site
Friday, 11 January, 13

16. Friday, 11 January, 13

17. Friday, 11 January, 13

18. Friday, 11 January, 13

19. Finding hooks
• WordPress.org Codex (http://
codex.wordpress.org/)
• http://adambrown.info/p/wp_hooks
• Debug Bar + Debug Bar Action Hooks plugin
(http://wordpress.org/extend/plugins/debug-bar-
action-hooks/)
• Search core (use your IDE or a command line
tool like ack)
Friday, 11 January, 13

20. Some pro tips
Friday, 11 January, 13

21. Use built-in APIs,
don’t re-invent the
wheel
Friday, 11 January, 13

22. Use WordPress coding
standards
Friday, 11 January, 13

23. Be nice to other devs.
Namespace your classes
and functions. Leave
hooks for others.
Friday, 11 January, 13

24. Demo time
Friday, 11 January, 13

25. Friday, 11 January, 13

26. Friday, 11 January, 13

27. Friday, 11 January, 13

28. Friday, 11 January, 13

29. hey that’s the
!le we want to hook
into
Friday, 11 January, 13

30. Friday, 11 January, 13

31. Friday, 11 January, 13

32. Friday, 11 January, 13

33. Friday, 11 January, 13

34. Let’s create our
plugin
Friday, 11 January, 13

35. Friday, 11 January, 13

36. Friday, 11 January, 13

37. Friday, 11 January, 13

38. Friday, 11 January, 13

39. Friday, 11 January, 13

40. Friday, 11 January, 13

41. Friday, 11 January, 13

42. Friday, 11 January, 13

43. It works, now let’s
have some fun
Friday, 11 January, 13

44. Friday, 11 January, 13

45. Friday, 11 January, 13

46. Friday, 11 January, 13

47. Friday, 11 January, 13

48. Finished plugin
Friday, 11 January, 13

49. A word on
Security
Friday, 11 January, 13

50. don’t trust
users
Friday, 11 January, 13

51. sanitize input,
escape output
http://codex.wordpress.org/Data_Validation
Friday, 11 January, 13

52. protect users from
malicious attacks,
use nonces to
validate user actions
http://codex.wordpress.org/WordPress_Nonces
Friday, 11 January, 13

53. Plugin
Distribution
Friday, 11 January, 13

54. Friday, 11 January, 13

55. Friday, 11 January, 13

56. Friday, 11 January, 13

57. Further
reading
Friday, 11 January, 13

58. Friday, 11 January, 13

59. Friday, 11 January, 13

60. Friday, 11 January, 13

61. http://www.wrox.com/WileyCDA/WroxTitle/ http://www.packtpub.com/wordpress-plugin-
Professional-WordPress-Plugin- development-cookbook/book
Development.productCd-0470916222.html
Friday, 11 January, 13

62. Thanks!
Q&A
http://slides.jkudish.com
Friday, 11 January, 13