This document discusses plugin development in WordPress. It explains that plugins should be used for custom functionality rather than themes to avoid losing data when changing themes. It provides resources for a custom plugin project on GitHub and covers topics like activation hooks, deactivation hooks, using hooks, adding shortcodes, and including styles in a plugin. Contact information is provided for questions.

1. PLUGIN
DEVELOPMENTJason Yingling (@jason_yingling)

2. CUSTOM FUNCTIONALITY
PLUGIN VS THEME
Plugins should be used when adding custom
functionality to a WordPress site.
If you add a post type in a theme but switch themes
later you “lose” that data.
Plugins can stay with the site regardless of theme.

3. OUR
RESOURCES
We’ll be building the custom plugin available here:
https://github.com/yingles/stl-meetup-plugin

4. PLUGIN DEVELOPMENT
GETTING STARTED

5. PLUGIN DEVELOPMENT
ACTIVATION HOOK

6. PLUGIN DEVELOPMENT
DEACTIVATION HOOK

7. PLUGIN DEVELOPMENT
USING HOOKS

8. PLUGIN DEVELOPMENT
SHORTCODE
Next we’ll add a shortcode that pulls data from another
site using the WordPress REST API

10. PLUGIN DEVELOPMENT
ADDING STYLES

11. PLUGIN DEVELOPMENT
QUESTIONS
Twitter: @jason_yingling
Email: jason@jasonyingling.me