I don’t talk about user interface design much because it’s not my forté. I’m all for people working within their core strengths and then hiring them when needed on a project-by-project basis (if the designs aren’t already provided).

But when it comes to working with WordPress administration screens, there’s a difference, right?

I’m on the mindset that because the WordPress administration area has a consistent look and feel, then anything that’s built to work within the administration screen (such as a settings screen) should look as close to the core UI as possible.

Not everyone agrees, and it’s evident by the vast array of plugins that are available. But that’s my position on it.

Periodically, I’m asked how I structure the UIs of projects when they need administration screens and how I map them to files within the project.

So I thought I’d take a simple example and break it down in this short post.

Continue reading

Talking about CodeKit and the benefits it offers for front-end developers has also come just after a post and the benefits that something like Gulp offers, as well.

A post on the difference between the two, why you may want one over the other, and the advantages or disadvantages of either can be its post.

But for this, I’d like to take the starter packages I wrote about regarding Gulp and give a simple example of a starter Gulp file and how to use it in your WordPress projects.

Continue reading

If you have a custom meta box or are working with custom metadata at the post-level, then you may stumble across a problem with having data accidentally deleted when saving it from the Bulk Edit screen.

The setup for the problem is something like this:

1. you have a collection of posts that need to be changed,
2. you load all posts in the bulk edit screen (as shown above),
3. you apply a change.

Once this happens, the change occurs, but it erases any custom post metadata that you may have.

Continue reading