I’ve written several posts about WordPress meta boxes. Perhaps the series of posts closest to what I’m going to touch on in this post is the one that outlines:
1. Aiming For Simplicity
2. Separating The Logic
3. Each Component
4. The Front-end
You can read each of these if you want, but they aren’t necessary for this particular post. If you’re familiar with WordPress meta boxes and how to create them programmatically, then you should be good to go.
The short of it is this:
There’s a consistent way to create WordPress meta boxes in an object-oriented way. This includes an interface, defined methods, and permission and security checks.
A lot of people who work with WordPress use third-party code to create these features. This includes other plugins or generators. That’s fine. I’d say that falls more into the implementor camp, but that’s beside the point.
Further, it’s not the point of this post. Instead, this post focuses on concepts for WordPress developers looking for object-oriented solutions.
Throughout the last few posts, I’ve been talking a little bit about WordPress Developer Salaries, but have also done so by taking a look at exactly what it means to be a WordPress developer. If you’re just catching up, the previous posts are: A WordPress Developer Salary Should Be…? WordPress Developer Salary: Manage That Content […]
In the previous post, I shared a few thoughts on the challenges of setting a WordPress developer salary. When I began writing out my opinion, I ended up writing a lot more than I had intended, so in order to keep posts at a shorter length (thus saving all of us time :) and sounding […]
Earlier this week, Ryan Sullivan – a twitter-friend of mine – sent out the following note: Interesting. Add “WordPress” to almost any development job search and watch the salary magically drop 30%. Any thoughts why? — Ryan Sullivan (@ryandonsullivan) July 14, 2014 An interesting observation, isn’t it? Especially for those who work on WordPress full time, work with WordPress […]
One of the words that has begun to surface in the software development community in the last few years is craftsman. I attribute this to Uncle Bob Martin, his Clean Code book, and his whole Clean Coder movement (for lack of a better term). I want to be clear: I love this idea. I’m a fan of […]