[…] now differs from how I wrote my code when I was working on those projects. And surely you know what I’m talking about: It’s not that the plugins don’t work and it’s not that they necessarily cause problems for anyone, but the open source nature of what they don’t necessarily represent what we’re capable […]
Search: “plugins” (Page 70 of 130)
We found 650 results for your search.
[…] WordPress, this is a person who knows how to find something that gives your site a certain look and feel (a theme), and how to install certain plugins (to introduce functionality), but they aren’t capable of writing code on their own to bring the project to life. There are a number of ways to […]
[…] or function names until they find where something breaks (or changes) Some use debugging software (or the debugging features in their IDE) Some use a combination of plugins and other techniques And some likely use some strategy that isn’t listed here Personally, I’m partial to using some of the developer tools that are provided […]
[…] is, points during the WordPress life cycle that allow us to add our own functionality to customize how WordPress behaves. Of course, this is how both themes and plugins are made to do some of the neat (or not so neat, depending on the project) things that they do. And though I obviously recommend reading […]
[…] of the Boilerplate, thankful for the people who have contributed to it thus far, and am happy that others have found it useful in both building their plugins and in using it as a way to learn more about WordPress development. When it comes to maintaining an open source project, four years isn’t a long […]