Tag: WordPress (Page 195 of 219)

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

A Case Against WordPress Shortcodes

March 6, 2013 / Tom / 0 Comments

At my recent WordPress Developer Meetup, the topic of shortcodes came up as a point of discusion. When talking about it, I realized that I’ve never actually talked about them here on the blog, so I thought it might be worth bringing up for discussion.

For those of you who have seen any of my plugins, you see that none of them include shortcodes despite the fact that people have requested functionality offered by them.

For the most part, I dislike WordPress shortcodes. I think they are unintuitive, difficult to use for the average user, and go against much of what the core functionality of WordPress aims to offer.

But the challenge is that there’s not yet a suitable alternative.

Some Thoughts on Building WordPress Plugins

March 4, 2013 / Tom / 0 Comments

With the exception of Standard and contract projects, I generally don’t build WordPress themes for release.

I tend to favor plugins because I’m attracted to the functionality that they are able to introduce to the core WordPress application and, frankly, I don’t have the design chops required to produce a theme of high enough quality.

Simply put, I try to focus on what I’m good at doing so others can do the same.

Last week, I talked about the problem of offering support for free WordPress plugins, the challenges that I’m currently facing, and ultimately what I’m aiming to do about it.

So in keeping consistent with trying to share my general thought process on both plugin development and moving to a better business model, I thought I’d also share some thoughts on building WordPress plugins. Continue reading

Support Doesn’t Scale (or “Avoid Free WordPress Support”)

February 26, 2013 / Tom / 0 Comments

Recently, I’ve been talking quite a bit about profiting from open source software, strategies for supporting WordPress plugins, and debating just how much to support to offer.

To say that I’ve been exploring business models and support offerings for my plugins would be a bit of an understatement. Clearly, this has been something that’s been on my mind for the last few months.

The thing is, this won’t be the first time that I’ve ventured into this territory. In fact, I’ve done this for two plugins – WP Social Icons and Author Admin – that I retired some time ago. Ultimately, I want to make sure that if I do this again, I do this right.

But while I’m still working on the logistics of everything, I thought it’d be worth sharing why I’m even doing this.

Quite simply: Support doesn’t scale.

A Look at The UI Design Process in WordPress Plugins

February 22, 2013 / Tom / 0 Comments

I’m no designer. I don’t aspire to be one, nor do I claim to be one that; however, I am interested in the topic and enjoy seeing the work that others do as well as following blogs, articles, books, etc. on the topic.

Though user interface design is a bit of a different field, it hits much closer to home for me than other types of design. After all, a user interface is basically the face of the code that we’re writing.

And if we’re not careful, then we’re going to continue perpetuating the stereotype that developers do not care about design.

I’ve spoken previously about sharing case studies on WordPress projects, and though I don’t have a full project to share right now, I thought it might be fun to look at some I’ve been working on and the evolution of a particular user interface that evolved from a first pass, to discussion, then from mockup, to implementation.

Object-Oriented WordPress Plugin Development

February 21, 2013 / Tom / 0 Comments

When it comes to writing plugins – specifically those that are object-oriented in nature – many of us do so because we’re obviously fans of writing object-oriented code.

Personally, I’m a fan of it because it helps to separate the responsibilities and concerns of a requirement into its own logical unit.

Sure, this can be done with several function files as well, but I come from an object-oriented background, so when I approach a problem, I automatically begin thinking in terms of classes and their relationship to one another.

And I know that other developers do the same.

The thing is, I think some of us – myself included – have gotten lazy or we only half-bake our object-oriented-based plugins. That is to say that we may be using classes in writing our plugins, but we don’t do such a good job of taking advantage of other object-oriented principles and features.