Tag: WordPress (Page 168 of 220)

Articles, tips, and resources for WordPress-based development.

How Not To Market WordPress Products (or “Why Customers Don’t Care”)

April 1, 2014 / Tom / 0 Comments

If you’re any sort of a WordPress developer, then one of the things that you’ve no doubt noticed is how we market our work.

I’d say that it can be divided into two camps:

You have the developers who promote the features, design, and options that the theme or plugin offers.
You have the developers who promote all of the things that have gone into the theme as to what makes it significant.

When it comes to marketing WordPress themes or plugins (or any product, for that matter), then the first group has it absolutely correct.

The second group, on the other hand, can take a few cues from the first group – namely, stop trying to market your WordPress products based on the tools and technology that were used when working on the project.

Using WP_Query To Get Posts From Last Week

March 27, 2014 / Tom / 0 Comments

One of the most powerful aspects of the WordPress API is WP_Query as it allows us to retrieve a wide variety of content through a relatively simple interface.

That is, it allows us to retrieve complicated datasets ranging from custom post types, post status, date ranges, taxonomies, meta data, categories, and so on all with a relatively standard set of PHP constructs (mainly arrays) and with a really solid reference in the associated Codex article.

One of the nicest things about WP_Query, especially since WordPress 3.7, are the advanced date query parameters that we can use in order to retrieve information from a specific date range without having to do a lot of complicated date math (which, of course, is every programmer’s favorite aspect of development).

If you learn how to use that particular aspect of WP_Query and you’re familiar with PHP’s strtotime function, then you can retrieve posts from a range of dates easily.

Bug Ticket Triage for WordPress Themes

March 26, 2014 / Tom / 0 Comments

One of the things that I try to do with my projects is to create quick, iterative releases. When it comes to client work, I’ve made a lot of progress with this over the past year; however, when it comes to working on products (be it plugins, themes, or something similar), I’m not as good as I’d like to be.

Nonetheless, I’m still working on it and one of the ways in which I’m trying hard to focus on that is through creating a system of bug ticket triage.

Sounds all fancy, right?

Sounds fancy.

It’s not :).

Basically, it’s a way that I sort tickets as they come into the support channel and decide how I’m going to be resolving them according to their level of severity.

Though I don’t think there’s a definitive way to do this, I thought it might be worth sharing how I’ve been doing this with Mayer (as well as some other client projects) in order to try to create the leanest release experience possible.

A Practical Example of The WordPress Heartbeat API

March 21, 2014 / Tom / 0 Comments

The WordPress Heartbeat API is not exactly a new feature. That is, it was first released in WordPress 3.6. Maybe I’ve just done a poor job of keeping up with what others are doing with the API, or maybe I’ve just not paid attention to some of the stuff that people are doing with the API, but I haven’t seen that many examples other than how to get started with it.

On top of that, the Heartbeat API codex is lacking in documentation (though this is an open source project, so if anyone’s to blame, it’s all of us), so perhaps that’s a reason that few people have begun to implement it into their projects.

Whatever the reason, I thought it may be worth showing a practical example of how I recently implemented it within a theme I’m working on, and how I’m using it within conjunction with the Theme Customizer so that when an administrator makes a change to the theme using the Theme Customizer, the visitor will automatically (or is it automagically?) see the changes.

Should There Be Developer Documentation for WordPress Themes?

March 17, 2014 / Tom / 0 Comments

For anyone who has been involved with building and/or supporting WordPress themes, then it can’t be understated how important documentation for WordPress themes can be for customers.

Generally speaking, this type of documentation refers to a manual that walks users through how to use a theme, it’s various features, and so on. I think it’s hard to argue that this is something that should be made available for everyone, or, at the very least, for those who have purchased the theme (of course, having a freely available manual can also serve as a marketing resource, but I digress).

But one thing that I don’t think talked about very often is if there should be developer documentation for WordPress themes.