Software Engineering in WordPress, PHP, and Backend Development

Author: Tom (Page 100 of 427)

WordPress Data Collection with EZ Data

Usually, whenever I share resources on this site, it’s for development-related tools. Sometimes it’s plugins, other times; it’s things that we may use that are tangentially related to our work.

Sometimes, I’ll publish things from peers in the industry who I don’t know; other times; it’s from people who I know, consider a friend, and respect.

And the latter is the case with Roy Sivan and EZ Data.

Continue reading

How to Use PSR-4 Autoloading WordPress Plugins

Say that you’re working on a project for someone and you’ve scoped it out, tasks are delegated, you have all the libraries and tools you need to get started, and you’ve separated what will be the theme or presentation, and what will be the functionality or the plugins.

But rather than having a handful of individual plugins, what if there was a package of smaller functional plugins or micro-plugins or whatever you want to call them working to power the package?

PSR-4 Autoloading WordPress Plugins: Example Organization

Furthermore, these all of which are built on the same foundation but that also share code with one another and to make things more interesting, you opt to use a PSR-4 autoloader via Composer to take care of all of this?

Continue reading

Configuring Composer for WordPress, Part 2

In this post, I’ll wrap up what I began to share yesterday: Using the tools and libraries I’ve shared in conjunction with Composer to sniff your commits during development before the code hits the repository.

Ideally, you’re always going to want to see something like this in your terminal whenever you commit your code:

Composer for WordPress, Part 2: Configuring Sniffs

But that’s not always the case. As with most things, though, the more you practice, the more you’ll get used to writing code that will automatically pass the various sniffs put in place through the different rules (and their customizations).

Before doing that, though, you’ve got to get GrumPHP configured in your repository.

Continue reading

Configuring Composer for WordPress, Part 1

Okay, so after talking through all of the various libraries that can help improve the code quality of your work, it still raises a question:

How do we get these projects working against our code base?

In short, it requires Composer. If you’ve never used it, I’ve written briefly about it before, but I intend to provide the basics of what you need to get started using it and the aforementioned libraries in your work.

In both this post and the next, I’ll share how to set up everything locally in the most basic form and then how it integrates with Git so you can start using it in your day-to-day.

Continue reading

Libraries for WordPress Plugins, Part 3

In the last three posts, I’ve talked about libraries for WordPlugins that I find to be extremely helpful in writing high-quality codebases.

If you’ve not been following along, you can either catch-up by reading the previous posts:

Or you can just review the list of tools I’ve listed thus far:

This post will wrap up the series with the final set of tools that we typically use when building solutions for others.

Continue reading

« Older posts Newer posts »

© 2025 Tom McFarlin

Theme by Anders NorenUp ↑