Semper fudge.
While I was in Austin last week, work graced me with a new set of business cards. And they’ve got my new(ish) title! Don’t they look fucking handsome?
I’m sure that everyone I hand them to will silently curse me for their non-standard size, but maybe that’ll become less of an issue once they notice the lightly embossed WP Engine logo.
Or maybe not. But hey, whatever. New cards!
SPOILER ALERT: The answer is always going to be “no”.
Much like Jeffro, I’ve found Incoming Links to be practically useless for the past few years, so I’m glad they’re finally killing the widget.
Pretty great presentation from Google’s Ilya Grigorik on how you can make pages display even faster for your visitors.
A comprehensive list of all the annoying, buggy shit that came along with iOS 7’s “upgrade” to Safari.
Finally, a well written set of plugin tutorials for beginner and intermediate developers.
I’m totally fucking thrilled that 3.7 is using Dropbox’s zxcvbn library to fix the password strength meter.
This reminds me a bit of Medium’s editor. Mainly the darkness. But I still really like it. I honestly hope they get enough work done on the plugin to ship it in 3.8.
A plea for developers to quit being condescending assholes, by Tom McFarlin.
Voce Platform’s Ansible playbooks for their scalable WordPress configuration, Afterburner. Even if you don’t use the playbooks, there’s tons of great config tweaks that can be found by digging through the code.
Ridiculously handy custom post type cheat sheet from Justin Tadlock.
This is going to possibly piss off a lot of half-assed plugin developers. But it’ll also be a big fucking deal if it makes it into 3.7 unscathed.
Great article from 10up’s Jake Goldman on the future of WordPress as an application platform.
It’s still not 100% production ready, but it gets that much closer with every release.
This version brings user selectable color schemes and a new way to set scalable/colorable custom icons. Very nice.
I get people’s apprehensions towards the automatic update feature coming in WordPress 3.7. Developers tend to be pretty skittish about turning over control of any part of their site to someone else.
In the comments on this piece at WP Tavern, Nacin does a fantastic job breaking down why these calls for opting out of the updates by default are short sighted. I’d quote the whole comment here, if I could, but it’s a fairly long one. Instead, here’s a few key points.
If the next version of WordPress comes with a feature that the majority of users immediately want to turn off, or think they’ll never use, then we’ve blown it. To take it further: Any time you add a feature that defaults to off, why bother?
…
We can be really smart about this, like not doing auto updates when it doesn’t make sense to — such as when we can detect we are a Git clone or SVN checkout, or when updates are blocked from the UI, or when the web user isn’t the owner of core files. But I fail to see why, given the technological ability of pushing the button for you for security releases, we’d get almost all the way there then just add a checkbox. That’s a cop-out.
Fuck yeah, man.
While it’s rare for me to encourage people to go read the comments anywhere, you should really do that in this case. Especially if you started to form even a minor opinion about this feature.
The first set of mockups reimagining the WordPress dashboard is up on Make/UI, and they look nice.
I’m looking forward to using this. Just as soon as they make it into an actual plugin, that is.
It would appear that selecting only “Published” posts in the WordPress exporter means that attachments don’t get exported. Because why should they? It’s not like your posts might use them or anything.
TL;DR: The number of plugins you have doesn’t really matter if they’re well coded.
If every entry level tech support person at every shitty hosting company would read this, we might be able to get somewhere.
Finally, a WordPress tutorial that doesn’t involve adding something to your theme’s functions.php file. How refreshing. ᔥ
A very well done 1X web browser for those Mac folks that have one of those fancy Retina MacBooks.