Software Engineering in WordPress, PHP, and Backend Development
Comments are closed on this post. Please keep the discussion on the original post.
Last week, I had the pleasure of hanging out with Jeff Chandler and Sarah Gooding of WP Tavern on the WordPress Weekly Podcast.
We talked about WordPress – naturally – various headlines in the WordPress community, remote working, and some other fun topics.
Today is an official holiday in the United States, so I’m taking the day off of the usual routine.
For those of you who are in the United States and are celebrating Thanksgiving, I hope you guys have an awesome day hanging out with your family, friends, eating, sleeping, and generally enjoying the day off.
Happy Thanksgiving, guys!
Anyone that does design or development (or even writing, really) as either a hobby or for a living knows that feeling of going back and looking at their old work – and cringing.
We know that we’re making progress in our work when we look at something we once did and think “What was I doing?”
The funny thing is, whatever we’re designing, developing, or writing today is going to be treated that way sometime in the not-so-distant future, right?
I digress on that point.
Anyway, for me, one of the things that I find myself debating is how long I should keep some of my open source code repositories around.
WordPress’ `post_class` function makes it really easy to write out a variety of class names to post containers that give us a finer-level of control when working on styling WordPress posts.
But there are times in which you may want to actually add a custom class to a post (or to a single post) depending on the nature of the content of the most.
And sure, you can easily add additional parameters to the `post_class` function, but those are still static parameters that will be applied to every posts.
What about in cases where you want to add a class if, say, no more tag is present in the content?
Comments on this post are closed. Please leave comments on each article's respective page.
As WordPress continues to grow in popularity and continues to evolve as a web application, developers are beginning to see how it can be used for web application development.
This isn’t to say that it should replace any of the frameworks or foundations that are already available, but that it should be considered as a serious contender for certain types of web applications.
In my latest series on Envato, I’m going to be taking a look at what it means to use WordPress for web application development, how it differs from existing frameworks and foundations, how to think about it in the context of design patterns, and why its existing facilities provide a solid foundation outside of the box.
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 ↑
