This weeks episode features Chris Cochran, co-organizer of Wordsesh. In this episode, we discussed the inspiration behind the event, Wordsesh 2, what may be coming with Wordsesh 3, and much more. We also talked about the release of WordPress 3.8, covered all of the new features and gave our thoughts on the new default theme, TwentyFourteen. Last but not least, I challenge you to figure out whether the sound you hear in this episode is a baby, or a kitten. Leave your answer in the comments.
Stories Discussed:
WordPress 3.8 Released
Get More Admin Color Schemes For WordPress 3.8
Coming Soon: An Issues Tracker for WordPress Documentation
Jetpack 2.7 Introduces Google+ Publicize Support and Adds Cloudup oEmbed
Envato To Re-Focus On Community After Lifetime Earnings Reach $140M
WordSesh 2 Video Playlist
WPWeekly Meta:
Next Episode: Friday, December 20th 3 P.M. Eastern – Special Guest Chris Lema
Subscribe To WPWeekly Via Itunes: Click here to subscribe
Subscribe To WPWeekly Via RSS: Click here to subscribe
Subscribe To WPWeekly Via Stitcher Radio: Click here to subscribe
Listen To Episode #131:
[powerpress]
This change is minor in the overall scheme, but it is the latest example a recurring pattern of removing/changing a user option without particularly good reason, and without communicating the change to the end user.
I totally understand the decisions, not options philosophy; but once the decision has been made to provide the end user an option, that option should be treated as – if not sacrosanct, at least important enough that a later decision to remove that option must have a very, very good reason.
The number and width of columns in the dashboard are a simple matter of CSS. There’s absolutely no reason that the dashboard can’t accommodate both a responsive design and the user configuration of number of columns. (How about: simply rename “Number of Columns” to “Max Number of Columns”, and an explanation that number of columns depends on available width? Most people are now familiar with layout changes caused by responsive design, and would not be caught off-guard by multiple columns reducing to a single column on smaller screens.)
But even if there were a very, very good – and valid – reason to remove a user option, users shouldn’t have to find out about that change by happenstance. This change wasn’t communicated (at least as far as I noticed – and I do try to keep up with version-to-version changes.)