Author: Tom (Page 376 of 427)

Version Numbers: What’s The Point?

October 3, 2012 / Tom / 0 Comments

One of the things that my team and I have consistently discussed when working on Standard is how to actually maintain or version numbers. It doesn’t stop there, of course – even in my own work, I give considerable thought (how lame does that sound?) as to how I should track the version numbers of my projects.

Thought I tend to follow the schema of “Major Version, Minor Version, Hot Fix” (i.e., 3.0.2), I’m unsatisfied. And to put it bluntly, I’m discontent with the whole thing version numbering issue: They’re inconsistent, they aren’t user-friendly, and I’m not even sure what we should do about it.

Five Suggestions For Writing Better JavaScript in WordPress

October 2, 2012 / Tom / 0 Comments

This is the final post in the series JavaScript in WordPress. Be sure to read the first article, too!

In the first post in this series, I briefly mentioned that there is a problem with writing JavaScript in WordPress. In boils down to the fact that people are writing JavaScript who don’t truly know jQuery (let alone JavaScript), and that there are lack of standards to follow.

And though I’m not interested in defining the coding standards for JavaScript in WordPress – at least not here – I am interested in sharing four things that I’ve found to be successful in writing maintainable jQuery in WordPress for both individual and team-based projects.

Note, of course, that these are geared towards jQuery. After all, that is WordPress’ JavaScript library of choice.

The Problem of No Coding Standards For JavaScript in WordPress

October 2, 2012 / Tom / 0 Comments

This is the first post in the series JavaScript in WordPress. Be sure to read the final article, too!

One of the challenges of building projects on top of WordPress is that there are well-defined coding standards specifically for PHP-based components. There are even some guidelines for HTML, and the CSS guide is under construction, but there appears to be very little in way of coding standards for JavaScript in WordPress.

I’m certainly not going to be defining those standards here – that belongs in the Core Contributor Handbook, right? – but I am doing to be sharing my thoughts on JavaScript in WordPress and some of the things that I do in order to make sure that my projects and that my team’s projects are maintainable over time.

Introducing #notes For Capturing Blogging Notes

October 1, 2012 / Tom / 0 Comments

Occasionally, I share some of the work that my team at 8BIT has been working on. Up until recently, we were focused heavily on Standard for both self-hosted blogs and for WordPress.com.

The thing is, we’re not trying to be another theme shop. In fact, our ultimate goal is to try to make the best products possible for people who consider themselves to be or who are aspiring to be digital publishers.

This may include developers and designers, but more often than not, this includes people who care about sharing their thoughts, opinions, views, and general words about any given topic.

And we want to empower them.

The challenge, though, is that we don’t always have our digital devices with us, but for anyone who has blogged for a significant amount of time realizes that inspiration or ideas can hit at any time.

To that end, we saw a need to help others take blogging notes. Friday, we officially announced, released, and began shipping #notes. Continue reading

How To Use WP_User_Query For WordPress User Queries

September 28, 2012 / Tom / 0 Comments

Earlier this week, I published a post on how to find users in WordPress by using meta data. In short, I have a collection of users each of which have unique meta data and I needed to locate a user based on said meta data.

In the comments, Curtis of @WPThemeTut recommended I check out WP_User_Query as opposed to way that I was doing it (which I’ll cover momentarily).

Because the WordPress API has a tendency to introduce new functions for querying specific data in later releases, and because I try to be a proponent of using the newer methods, I wanted to cover WP_User_Query in a bit more detail.