Software Engineering in Web Development, Backend Services, and More
Articles, tips, and resources for WordPress-based development.
Comments are closed. The winner has been selected and contacted. Thanks to all who participated!
Back in December, the team at ThemeFuse was kind enough to offer a giveaway and have offered to do the same again this month.
Since I try to take advantage of certain opportunities that help benefit those of you who are budding and/or experienced WordPress bloggers, designers, developers, and so on, I thought that it would be a good idea to go ahead and take them up on a second offer.
I could completely be in the minority in what I’m about to say, but when I see phrases such as “The WordPress Admin,” I cringe a little.
Maybe I’m being a bit legalistic, but hear me out: All throughout the backend of WordPress, we see the phrase “Dashboard.” In fact, it’s the first menu item that we see.
Comments are closed as the winners have been selected and emails. Thanks to all who participated!
One of the more popular services that has to come to WordPress within the last year or so is the ability to integrate Git into your theme, plugin, and/or application development workflow.
And why shouldn’t it?
Services like GitHub and Bitbucket are responsible for the rise of Git, has introduced many people to source control (who I wonder if they’d ever use it), and then third-party services have made it possible for other people to connect their repository to another environment and deploy the changes.
It completely cuts out the middle-man of S/FTP and makes sure that we’re able to deploy true changesets of our work so that the code that’s sitting in our staging (or even production) areas are as updated as possible.
I’ve been using Postmatic to manage my blog comments for quite sometime now – since November, even. In fact, I’ve written two previous posts about the plugin:
Since those posts, I’ve continued to run Postmatic – I’ve been through every single release of the beta, I’ve been through the release candidates, I’ve experienced the bugs that come with it (and I know some of my readers have as well – thanks for the tweets on those, by the way :), and I’ve been through their resolution.
To say that I’ve not experienced each hill and valley of the business as a customer since last November is an understatement. The fast turn around and direct communication with Jason and the rest of the development team couldn’t be better.
Other companies could take note, but that’s another post for another day.
Today, Postmatic has officially hit 1.0 and I couldn’t be more excited for the team.
This is the final post in a series on An Object-Oriented Approach To The WordPress Settings API. Part 5.
Over the last few posts, I’ve covered topics ranging from creating interfaces to base classes and how to implement and inherit from both. One outstanding issue with the approach that this has covered thus far is that it didn’t take into account any type of file organization.
Anyone who has worked with any project of any size knows just how important having a clear organizational structure can be.
Later versions of PHP have feature of namespaces which can help us to further organize the code, but if you’re having to work with an old version, you don’t have that luxury. That’s no excuse for not properly organizing your files, though. You can still mimic what the namespace organization may look like.
So in this final post, I wanted to cover the approach that I normally take when organizing a plugin like the one we’ve been building.
Kinsta offers premium managed WordPress hosting for everyone, small or large. Powered by Google Platform and strengthened by Cloudflare, they take performance to the next level. All hosting plans include 24/7/365 support from their team of WordPress engineers. Get started with a free migration today.
© 2026 Tom McFarlin
Theme by Anders Noren — Up ↑