A listing and summary of all posts that I’ve contributed to the Envato WPTuts+ blog.

Getting Started with WordPress Taxonomies

Comments are closed on this post. Please leave your comments on the original article.

For those who are just getting started in WordPress development, one of the more challenging aspects of working with some of the extended APIs is that of WordPress taxonomies.

Perhaps it’s because the term is one that’s not often used, perhaps it’s because it’s something that’s a little difficult to understand; however, whatever the case, I’m aiming to try to simplify the topic in my latest series on Tuts+.

Yes or No To WordPress Frameworks?

Comments are closed on this post. Please leave your comments on the original article.

I don’t know if there’s ever been a time in WordPress-history where we’ve had such a plethora of options from which to choose as it relates to WordPress frameworks.

We have anything from drag-and-drop page builders to code-level abstractions that aim to make it easier to work with a variety of APIs.

But is using a framework always the best idea? Maybe. In my latest article on Envato, I weigh one of the pros and cons of using WordPress Frameworks in order to help determine if this is something that you may want to use or not.

Maintainable WordPress Meta Boxes

The comments on this post are closed. Please leave your feedback on each of the respective articles.

When it comes to enhancing the functionality of the CMS, WordPress meta boxes are one of the most flexible features that we can introduce to the post editor screen.

In short, they’re a way that we can open additional fields to one, some, or all of the existing post types as well as custom post types. They also make it possible to introduce a number of different type of elements – be it input fields, textareas, checkboxes, etc. – so that users can easily view, add, and/or modify data associated with a given post.

When it comes to writing meta boxes, especially those that are more elaborate than others, it can become a bit of chore to maintain the code over time. But it doesn’t have to be that way.

Writing Maintainable WordPress Code: Plugins

The comments on this post are closed. Please leave your feedback on each of the respective articles.

Regardless of the type of software that you build either for a living, for a hobby, or for both, one of the most challenging aspects of the field is trying to write maintainable code.

That is, code that’s organized, follows a standard, is easily read, and adapts to change over time as the environment and requirements of the overall software changes.

It’s not an easy task and people far, far more experienced than I am are still talking about how to do it.

Still, that doesn’t mean that those of us who have been working in WordPress for some time haven’t learned some strategies for works, what doesn’t, and what’s proved to be maintainable WordPress code throughout the years of development.

Working with the WordPress Media Uploader

Comments on this post are closed. Please leave comments on the respective posts linked from here.

Though I’ve talked about working with the WordPress media uploader in previous posts, I’m currently working through a series on Tuts+ that takes you through the process of incorporating the WordPress media uploader into your own plugin.

This post is going to serve as the landing page for the series of articles, but if you’re a beginner then this series should be for you.

The Beginner’s Guide to Type Coercion

This week, I started a new series on Tuts+ Code that walks readers through understanding type coercion.

Type Coercion

Type Coercion

Generally speaking, the series of articles starts at the most basic level by discussing strongly typed and weakly typed languages, data types and how they work in different environments, and then begins to branch out more into how data types work within dynamically typed languages.

The main motivation for this is because people who are coming from a strongly-typed background, or those who are just getting into programming may end up finding themselves making a few mistakes especially as it relates to comparisons, conditionals, and other similar evaluations.

This series aims to mitigate that.

Writing Maintainable WordPress Themes

Comments are closed on this post. Please leave your feedback on the series' respective article.

One of the most difficult aspects of building any type of software is the amount of work that’s required to maintain the project after its release.

Sure, shipping an initial version is challenging and this is not to understate the amount of planning, feedback, iterating, and general work that goes into a project; however, once it’s out in the wild and more and more people begin to use it, discover bugs, hammer on it, and so on, and additional ideas for features are developed, it becomes an entirely different challenge to keep the project rolling.

And though people would argue whether or not WordPress themes (or plugins or any script-based utility, for that matter) constitutes actual software, the truth is that it’s still subject to the same rules and methodologies as different software projects.

As such, one of the challenges of theming is actually writing maintainable WordPress themes such that they can continue to be improved over time. So in my latest series for Envato, I’m writing exactly on that topic.

Publicly Display Post Meta Data in WordPress

Comments are closed on this article. If you have something to add, please do so on the original article!

A couple of weeks ago, I shared a simple plugin that added a meta box to the post editor dashboard screen that demonstrated how to display post meta data within WordPress. After it was released, I received a few questions as to how one would go about displaying this information on the frontend of a WordPress blog.

That is, how would one go about displaying the post meta data as part of the content for a single post (or post type) in WordPress.

Though I’m not necessarily a fan of doing this, I am a fan of giving other developers practical advice on how to extend existing plugins (using practices used throughout an existing plugin), and I’m also a fan of discussing why I am a fan or not a fan of doing something.

So in my latest article at Tuts+ Code, I did exactly that.

Getting Started With WordPress

Last week, I had the opportunity to answer a question that I’ve often gotten via email, Twitter, meetups, and so on:

How do I go about getting started with WordPress?

It’s a simple question, to be sure; however, for those of us who are actively involved within the WordPress economy – or for anyone who has been involved in any development community, then you are more than likely familiar with how easy it is to forget what it was like getting started with the platform.

To that end, I wanted to provide some practice tips for how to do exactly that for the absolutely beginner.

Dealing with Custom Post Types, Taxonomies, and Permalinks

Comments are closed on this post. Please leave your thoughts on this original article.

One of the most confusing aspects of working with WordPress is managing its rewrite rules. For anyone who has taken a dive into the Rewrite API and looked at how it works, and how to customize it to fit your own needs can vouch for this.

Honestly, if you’ve ever done any work with custom post types, taxonomies, and permalinks and worked with the rewrite parameter (or perhaps have left it out), then you’ve experienced a little bit of the confusion (or frustration, perhaps) that can come with it.

For those who have been wrestling specifically with the latter, I wrote up a short guide for making sense of this occasionally confusing aspect of WordPress.