1. David Decker

    Yes, most will agree that the admin design of v2.5 was a fail and v2.7 “healed” that. And also in this heavy contrast lays the great feedback that v2.7 received.

    However, you’re painting a picture here that this version 2.7 was made by the community “mostly”. I don’t see it that way; “we” the users were given some surveys, yes, and that was new and great, really! In the end, however, it was a small group of core developers or “influencers” who made this release. But a few surveys aren’t a big community effort, if a small group still makes most of the work…

    I have voted in this one (or were it more than one?) survey about the admin icons, it was fun. I voted for the icon schema submitted by a German agency, which was second place in the overall voting and ended up being used for the blue color scheme in the admin.

    In my opinion, the fall release of 2013 with the new admin styles and the former “MP6” plugin were as much community driven as the 2.7 release – if not way more! Because of the widespread MP6 usage of the feature plugin, the users, the community could “smell” this release a lot more before and a lot of feedback found its way back to the “developer circle”.

    Every way of working out such releases has its advantages and its downsides of course. Given Matt’s new strategy and tactics for the next releases/ cycles I can’t wait what fruit is coming out of that. I hope for matured releases, that will have impact again for the long run (like 3.0 for example). It’s time that half-baked, slow solutions like the Customizer get a makeover/ rebuild, so that’s finally worth it. And if it’s not worth it, then cut it off and let new/ better ideas mature!!!

    One thing the 2.5 – 2.7 era shows: sometimes you need more than one iteration to hit the nail right. So let’s hope for next group of releases!

    Here’s my little list of areas where WordPress should improve:
    – frontend search!
    – admin search!
    – user management, user groups
    – editor/ writer tools, post status, whole publishing process
    – badge installing of plugins
    – make widgets no longer as options in the options table but somewhat better, maybe transform into a post type or whatever –> widgets as a flexible concept of content blocks, however, are awesome! :)
    – …


  2. Alex

    While it’s easy to declare 2.7 a grand success, it’s greatness is defined mostly by the weakness of 2.5. It is to me symptom of a long and ongoing issue with how WP gets developed.

    2.5 was the “we know better” update. It put something in place that, while seemingly good, was in fact a real negative for many. The tools were okay, but the design and layout wasn’t what people expected or particularly wanted.

    Consulting with the end users (via survey) gave you enough data to make a pretty solid leap forward, one which is effectively still in use today. That came from listening those people who use the tools, and not those who design them.

    The ongoing issue is one of “we know better”. Every so often WP take a solid left or right turn, often out of the blue, and seems to have left the public out of the process. It takes time for those things to get resolved and healed, usually a couple of versions later.

    The relative failure of 2.5 and the success of 2.7 should be food for thought every day, and something designers and programmers should always consider before just adding in the latest thing.


Comments are closed.

%d bloggers like this: