I’m currently on a fun little tour of Europe and I got invited to speak at the WordPress Meetup in Geneva, Switzerland this evening. I joined a group of about 20 developers, of all levels and talked about WordPress plugin development. We then opened up the floor for questions and had a great ongoing conversation about development in general, the WordPress ecosystem, the open-source nature of the project, multilingual solutions and I even taught the group some Quebecois swear words 🙂
The presentation is almost identical to one I gave in Winnipeg in the spring, the slides are available as a PDF from here.
Today I’m giving a presentation at WordCamp Victoria 2013 where I’m showing power users and novice developers how to get started with plugin development. I think a lot of people don’t realize how easy it is to get started with plugin development or just how small and simple can be. It doesn’t require 100s of lines of code…
Many WordPress tutorials out there talk about copy this or that to your functions.php file in your theme. However, it’s just as easy to create your own functionality plugin; which makes for easier to maintain code in the future that isn’t theme dependant. I begin this talk with the basics of what a plugin is and how it’s structured. I then explain the hooks (actions and filters API), followed by a very simplistic demo. I then give some pro tips and talk about some of the most commonly used WordPress APIs in plugins, as well as promote coding standards. A second more in-depth demo is then presented. Finally, I discuss security in plugins and share some resources for developers and users to further learn from.
Here are the slides from the presentation:
Let me know if you have any questions, using the comments below. And if you’re at WordCamp Victoria while you view this, come say hi!
Last march, Yannick Lefebvre, fellow WordPress developer from the Montreal WordPress community asked me if I would be willing to be a technical reviewer for a book he was writing. I was delighted by the opportunity and decided to take part in the project. And so for a few months, Yannick worked incredibly hard on getting a chapter ready every few weeks while I was giving him feedback on the code samples and explanations provided within his writing. It was definitely a unique experience since I don’t typical review literature in my day-to-day work.