An introduction to WordPress Development


Published on

The slides from my presentation to the Las Vegas Developers meetup group

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

An introduction to WordPress Development

  1. 1. An Introduction To WordPress Development by John HawkinsMonday, October 15, 12
  2. 2. I’m John I run / WordPress development I speak at WordCamps nationally I started the Vegas WordPress group (260+) I’ve got 1 wife, 2 kids, 1 cat, 3 dogs, self- diagnosed ADD and OCD. SQUIRREL!Monday, October 15, 12
  3. 3. The Misconception About WordPressMonday, October 15, 12
  4. 4. WordPress is Just For BloggingMonday, October 15, 12
  5. 5. That is... Wrong Not true Complete BS Erroneous False All of the aboveMonday, October 15, 12
  6. 6. What is WordPress A content management system An open source project Created by and for the community Free to use for anything from a personal blog to a Fortune 500 web siteMonday, October 15, 12
  7. 7. .com vs .org .com is a service .org is downloadable provided by a For software you can use Profit company on any server .com doesn’t allow .org allows unlimited install of your own freedom to do as you plugins / themes wish .com is updated for .org requires you you automatically update the software yourselfMonday, October 15, 12
  8. 8. Why I Use WordPress 70,000,000+ sites = big pool of clients Easy to use for end users Helpful community / access to support Can be made to do most anythingMonday, October 15, 12
  9. 9. Let’s Get Started But first, a couple rulesMonday, October 15, 12
  10. 10. The First Rule of WordPress DevelopmentMonday, October 15, 12
  11. 11. The First Rule of WordPress Development You do not edit core filesMonday, October 15, 12The reason for this is that WordPress typically releases 3 major updates per year along with a handful of securityreleases. Any core files you edit will be overwritten with the standard WP upgrade process
  12. 12. The Second Rule of WordPress DevelopmentMonday, October 15, 12
  13. 13. The Second Rule of WordPress Development You DO NOT edit core filesMonday, October 15, 12Please see slide 11...
  14. 14. Standard WordPress StructureMonday, October 15, 12Unless you are making a change to submit as a patch to the core team, you should most likely only be messingwith files in the plugins or themes folders
  15. 15. Let’s Build a Plugin Plugins can be a single file or multiple directories of files Create a folder and a php file with matching name inside the plugins folderMonday, October 15, 12
  16. 16. my-plugin.phpMonday, October 15, 12This information is all you need in order to tell WordPress that this file is a plugin.
  17. 17. Monday, October 15, 12With that little bit of info, our plugin is ready to be activated. Although it won’t do anything yet.
  18. 18. Add a FilterMonday, October 15, 12Added a filter which is going to edit the content and run our function in a specified order
  19. 19. Create a CSS Folder & FileMonday, October 15, 12
  20. 20. Add an ActionMonday, October 15, 12We’ve told WordPress that when it enqueues the rest of the scripts, enqueue ours, too.
  21. 21. The End ResultMonday, October 15, 12
  22. 22. Some Plugin Resources Don’t write code that WordPress already handles Know your hooks and filters Check out the WordPress coding Standards, October 15, 12- Don’t reinvent the wheel- 1600 hooks and filters- Hooks are actions that fire at specific spots in the code.- Filters typically modify content before displaying it on screen or writing to the database.
  23. 23. Let’s Build a Theme Like plugins, a theme can be one or many files Themes add design to your site Themes can also add functionalityMonday, October 15, 12
  24. 24. style.cssMonday, October 15, 12This is the only info you need to tell WordPress about our theme
  25. 25. Monday, October 15, 12With that little bit of info, our theme is ready to be activatedwhat happens if we activate now?
  26. 26. Monday, October 15, 12D’oh! We didn’t add anything to our index file yet...
  27. 27. index.php Get started by adding the header/footerMonday, October 15, 12
  28. 28. Post Layout, part 1Monday, October 15, 12have_posts() checks page for available contentwhile have_posts will loop through each postthe_title() / the_content()
  29. 29. Post Layout, part 2Monday, October 15, 12This is displayed if no posts were on the page_e() allows for translations
  30. 30. Hey, We Have a Page!Monday, October 15, 12It may be ugly, but you can see the beginnings of our site.
  31. 31. Add Some StyleMonday, October 15, 12Adding the most basic amount of style, and activating our plugin
  32. 32., October 15, 12Knowing what template is being used is VERY important.
  33. 33. Some Theme Resources The WordPress theme community WordPress CSS Coding Standards, October 15, 12
  34. 34. Save Some Time, Create a Child ThemeMonday, October 15, 12Creating a child theme only needs the Template tagImporting the style sheet is a huge shortcut
  35. 35. Monday, October 15, 12the original twentyten theme with our plugin activated
  36. 36. Monday, October 15, 12The Child theme changes colors, moves menu location, moves sidebar, made it 3 columndoesn’t affect the parent theme at all
  37. 37. Questions?Monday, October 15, 12
  38. 38. Want to Learn More?, October 15, 12
  39. 39. Thank You! Email: Twitter: @vegasgeek Facebook: /vegasgeek I’m sensing a pattern...Monday, October 15, 12