I’ve been using using and developing on WordPress for almost 10 years. In all that time, the single most important (WordPress related) thing to happen to me was WordCamp Gold Coast 2011, which was held 5 years ago today.
Today marks two years since I joined Envato. Those two years have disappeared in a whirlwind, with so much happening in that time. I decided to pause for a moment, to look back at some of the highs and the lows.
There is mounting excitement over the WP REST API being added to core and rightly so! It is going to fundamentally change the WordPress landscape and open up all sorts of new possibilities. Developers are drooling over all the cool stuff they are going to be able to build. Exciting times!
When it comes to using the REST API with themes, it may not always be the best choice.
When WordPress 4.3 was released, it added the ability for users to set a site icon, also known as a favicon, in the Customizer. In the past, users had to either add this manually, through a plugin, or through the theme options (if their theme included this functionality).
In this post, I’m looking at the last of those scenarios. What should theme authors do now that WordPress itself offers the equivalent functionality?
16 Feb 2015: This post attempted to answer the ‘why’ of Jetpack’s bloat. On 23 January 2015, at Pressnomics, Matt Mullenweg talked about Jetpack being the reason that WordPress wasn’t in decline and a key factor in the fight against WordPress’s competitors. Although I don’t necessarily agree with this or that it makes Jetpack’s approach okay, I do absolutely believe that Matt believes this very strongly. It actually validates most of this post – although I now believe the driver is helping to grow the platform, rather than simple business benefits for Automattic.
Recently, there has been some discussion around whether Jetpack is bloated. Hmm, actually, we’ve been talking about that for years… Anyway, the interesting part to me isn’t whether Jetpack is bloated, it’s why Jetpack is bloated.
Here’s how to delete all the terms in a taxonomy, whether it be category, tags or a custom taxonomy. Most sites will never need to do this – and there are probably better ways to do this – but here’s the code anyway.
This page contains resources relating to my “Actionable Analytics” talk at WordCamp Melbourne on 27 April 2013.
Alternatively, you can download the slides in either of the following formats:
If you have any questions about the talk, feel free to ask. I’m pretty busy, so apologies in advance for any delay in responding, but I will try to answer genuine questions.
I’m probably most responsive on Twitter, but feel free to leave a comment here as well.