Tag: WordPress (Page 161 of 219)

This past weekend, notable, highly respectable [and former] Automattician Philip Arthur Moore wrote a fantastic article that’s been making it’s way through the usual suspects and circles entitled We’re Ruining WordPress (This Needs To Stop). 

But in the hopes that some of those of you who read this blog are fellow bloggers, publishers, readers, designers, developers, and so on, I wanted to link it here with you to make sure you didn’t miss it and because I hope it resonates with you.

In short: If you’ve yet to read it, I highly recommend it – it short, poignant, and will likely strike a chord with many of you who are looking to contribute to the WordPress economy, have a business within the WordPress economy, or who enjoy following the WordPress economy.

Many of the things that Philip outlines in his post is what we’ve seen happen in other economies, too: Just look at Google Play or the App Store and how little apps cost. Games that used to run us $30 – $50 on a given system now cost $4.99 to $9.99 and people still complain (and it’s not even worth talking about in-app purchases).

Anyway, as much as I enjoy writing about WordPress and the various facets that come with it, and as much as I enjoy doing so with the occasional meme and what not, this particular post hit home with me because I’ve been working in the WordPress economy for several years at this point, I’m getting ready to push forward with a new effort, and because I’ve been thinking about this for the last few months (and clearly more so over the last few days), I thought I’d write a WordPress theme developer introspective of sorts on how it feels to be a part of the WordPress theme developer economy, its challenges, what I want to see change, and what I plan to begin doing as soon as possible.

Continue reading

Before Google practically destroyed the word ‘beta,’ people used to go about getting feedback on their work through closed testing, tight feedback loops, and other forms of getting work in front of others in a closed group of people to see how a sample of users would interact (or just simply react).

Movie production companies still do this – they test audiences: They see how they react to certain actors, certain endings, certain takes, and all that fun stuff.

In software, we still do that, but we throw words around like alpha and beta to the point where they have no real meaning anymore. At one point in the life of projects, alpha testing was solely for an internal group of testers, then beta testing was when it was open to a small group of people in the public in order to gather more feedback and to shake out bugs. Then there were release candidates followed by the final version (or the 1.0).

After that, we rinsed, and we repeated it.

Now, far more people have access to alpha-level software, and projects usually remain in beta as a way to excuse any problems that may occur during the course of using the application. After all, it is beta, so it’s use at your own risk, right?

Anyway, I could say a lot more on this, but I digress.

Continue reading

If you’re in the business of creating WordPress plugins for yourself or for others, then it’s likely that you’ve done work with custom post types.

On top of that, there’s a chance that you’ve needed to introduce some functionality into a custom post type based on what’s selected in the plugin settings (which I discussed all of that fun stuff in a previous post).

And I’ve seen a number of different ways in which this is done: Some of them involve complexity such as reading the select post types into an array, iterating through the list, comparing the current post type, setting a boolean, and so on.

But there is a cleaner way that this can be done. I’m not claiming it’s the best way (perhaps you could share some insight on your opinions on this in the comments), but it’s way that I’ve found useful and that I’ve been using a few times over throughout several projects.

Continue reading

As I’ve been working through a number of different plugins both for myself and for client projects, one of the things that has started to become glaringly apparent over the last few projects is just how unintuitive WordPress plugin settings can be.

I know, isn’t a new idea, but bear with me because I’m not talking about your standard run-of-the-mill plugins that have a settings page or that may add some type of shortcode functionality to the editor (though that’s unintuitive unto itself).

Instead, I’m talking about plugins that include a little bit of both: settings pages, additions to custom post types, perhaps the additions of shortcodes or buttons to the editor, and so on.

Continue reading

Right now, there’s a lot of talk about themes and their place within the WordPress community. Generally speaking, I think that this is a good thing as it’s finally forcing theme designers and developers to thing more strategically about the products that they’re creating, releasing, and to think more critically about their target audience, marketing efforts, and so on.

There are some who believe the market has been saturated, and though I follow that train of thought, I don’t agree with it. Just because there are more product options, more companies, and so on producing themes does not necessarily negatively detract from the industry.

I think it makes it more competitive which, in turn, can make it more innovative (though it can also create more products that should never be on the market, but that’s the nature of an economy and I’d rather keep the post optimistic).

With that said, I don’t think that there’s any reason to be discouraged from entering the theme development space, creating a new theme company, or anything like that.

In fact, I think on the contrary.

Continue reading