WANTED: WordPress Professionals With a Passion for Education. Enquire Within. http://t.co/UyG6C7dc
— Wptuts+ (@wptuts) October 3, 2012
Yesterday, @EnvatoWP invited others to apply to begin writing for WPTuts+, the Envato WordPress site.
Category: Articles (Page 249 of 258)
Personal opinions and how-to’s that I’ve written both here and as contributions to other blogs.
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.
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.
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.
I think of one the biggest challenges that programmers face as we become more comfortable and well-versed in our programming language(s) of choice, is that we become intimately aware of some of the more clever things we can do with the code.
For example, one feature of dynamic programming languages is that they offer anonymous functions. They’re really powerful and you can do some really cool stuff with them, especially in JavaScript; however, this always introduces a tension:
Are we writing code to be clever or are we writing code for others to understand?
Since I spend the majority of my time working with and writing about WordPress, I thought I’d share my thoughts on writing WordPress code.
Kinsta offers premium managed WordPress hosting for everyone, small or large. Powered by Google Platform and strengthened by Cloudflare, they take performance to the next level. All hosting plans include 24/7/365 support from their team of WordPress engineers. Get started with a free migration today.