Week in review: Evolving the customizer, WordPress philosophies, and more

week-in-reviewI thought it’d be fun to try something new here. As you’ve probably noticed, I’ve been doing fewer link posts. That is the result of a good bit of thinking, strategic and otherwise. I’ll dive more into that later.

I’ll still do some long-ish form link posts, but I won’t be able to link all the things I’d like to share, nor can I cover it all with long form content. So, I want to try this concept of a weekend reads / week in review post, that I’ll try and post between Friday – Monday each week. These will largely consist of links to posts from other websites, with the occasional link to special Post Status bits I’d love for you to see.

Without further ado:

Evolving the customizer

Matt Wiebe works on Team Custom at Automattic, and has used the Customizer extensively for the last couple of years. His concerns are in regards to many aspects of the customizer: performance, architecture, UX, mobile considerations, and more.

His wrap-up hurts:

Some folks might be reading this and wondering why I’m not trying to contribute this vision to core. I love to, but I don’t think it’s possible architecturally, and particularly not in a backwards compatible manner. This is certainly a case where the optimal use-case on WP.com (new user signup, pre-picked list of themes) may not line of [sic] with the best user experience for core users. I might be wrong about this, thus this post. I would genuinely love to be wrong, but I’ve worked with the Customizer extensively over the past two years and I’m pretty sure I’m not.

I’m really interested in what others have to say about this. Up until reading this, I was under the impression (from my own experience and others’ notes) that the customizer has a promising future with WordPress. Matt’s post makes me re-think those assumptions.

That said, there’s a lot of activity around the customizer in Trac tickets; one of which approaches some of Matt’s concerns: a ticket that would provide a “window wrapper” to the customizer.

Matt’s post is a good reminder that we should never look at a single feature (especially its first iteration) as a silver bullet. At the same time, I believe the customizer is still a great advancement for WordPress and I’m sure it’ll keep getting better.

We’re ignoring the WordPress philosophy

Tom McFarlin has put together a great series on WordPress philosophies that we are sometimes ignoring. Definitely read through these:

WordCamp Europe tickets are on sale

WordCamp Europe’s second event will be in Sofia, Bulgaria September 27th – 29th. Tickets for the event are on sale now. This is a great opportunity to learn with more than 700 other WordCamp fanatics, and its probably the most notable WordCamp you could attend outside of WCSF, which will be a combo WordCamp / Community Summit event in October.

WordPress The Right Way

Tom Nowell is a developer at Code for the People. He’s recently released an open source book, called WordPress The Right Way. The book looks promising, and you can find it on Github.

Inspired by PHP The Right Way, a famous PHP book, WordPress The Right Way assumes that you have an understanding of PHP fundamentals, and goes in-depth on most aspects of intermediate to advanced topics in WordPress development. This is probably a great resource to send to someone that’s already a good developer, but is just stepping into the WordPress project.

Tips for selling services using WordPress

My friends at Sell With WP have put together some nice tips for if you want to sell your services using WordPress.

If you’re the type that doesn’t want to pay for a third party hosted service, these tips could be valuable, and a good way to eat your own dogfood if you do any level of eCommerce consulting for WordPress.

Yet another Tim Thumb vulnerability

Tim Thumb was a popular image processing script that was the source of countless WordPress hacks a couple years ago.

Since then, its use is diminished, but unfortunately it was revealed to have another 0-day vulnerability exposed. Fortunately, this one requires some special configurations to be exploited, but still, seriously just stop using Tim Thumb if you do.

WordPress movie titles gone wild

This is #thingswpdailywouldpost territory, but it’s been a lot of fun too. My frenemies at WP Tavern have put together a few of their favorite titles from the #WPmovies hashtag that exploded the past few days. I’ll have to put it on my resume to have made the top 25 list a couple times.


I hope you guys enjoyed this format. Depending on feedback, I’ll see about making it a regular thing, so let me know if you like it.