Looks interesting, and makes complete sense that the platform veers this direction. The changes will be big, but the product will be better.
While laid up feeling ill this weekend I decided to whip out a new logo and website design for my band, The Night Trotters. There is still a wee bit of tweaking to do, but it’s close to being complete. Check it out!
If you are not a fan of making your own theme, you can use the nifty Find Themes website to pick one that suits your needs. While I have built many a WordPress theme from scratch, on this site, I tend to try out different themes other people have made so that I can learn more about the whole process. Now that I’ve found Find Themes, you may be seeing the theme here change again very soon.
I’ve been using the MP6 plugin on this website for quite some time, and now it will be part of WordPress by default. It’s a good bit different from what you may be used to visually, but it is a much easier interface to use. I’m looking forward to it.
This year we have seen the dawning of the responsive design craze amongst web designers and developers. I remained skeptical about the trend, primarily because I was raised in the world of good usability and accessibility, and breakpoints and adaptive images seemed incongruous and presumptuous with the foundations of those schools of thought. While responsive design proponents like to say that multi-device adaptation is providing good usability, I disagree.
Relating to my favorite CMS, WordPress, the whole responsive design trend has rubbed me in even more wrong ways. I’ve watched designer after designer dive into responsive WordPress themes, and I’ve even tried using a few myself, only to leave me wondering…why?
This article has some great analyses on this exact topic, and it provides some good food for thought in regards to responsive design and WordPress. From the article:
My biggest issue with responsive design is that it is a reactive client-side approach which, in the context of a server-side content management system like WordPress, seems completely unnecessary.
What are your thoughts on responsive design and WordPress?
An older vulnerability that got ignored in 2007 is showing up again.
According to Acunetix’s Bogdan Calin, this particular vulnerability is exploitable through the platform’s XMLRPC API (through XMLRPC.PHP). Attackers could try and guess hosts inside each network they target, port scan those hosts, reconfigure internal routers and launch large scale DDoS attacks.
From the details it doesn’t sound extremely dangerous, but something that should be fixed sooner rather than later. You can bet that we will see WordPress 3.5.1 pretty darned soon!