how many wordpressers does it take to redesign an admin interface?

On Shuttle, again, I’m afraid I have to join in with seriocomic:

after a year and a bit, all you have is photoshop mockups? No code yet?

Nope. It takes five or six blokes eighteen months to come up with some pictures. I have no problem with that; I’m sure they’ve all had more important things to do and a hell of a job agreeing on anything at all. (Somebody mentioned in Khaled’s comments that he’s a bit over-effusive when talking about his colleagues — always a sure sign of backstage bitchery).

What’s strange is that Matt’s expected to code it all up on his own by Christmas (or whenever 2.5’s slated for release). This seems sort of lopsided to me, especially since CSS and XHTML aren’t his specialist area and he’s got several other sites to run. It’s not like people haven’t offered to help, but, well, everyone should have twigged by now that he doesn’t do delegation. And now Kubrick Guy is fanning the flames by posting his own copies of the mockups that were in place before Khaled did a Matt and decided to tackle everything himself, so that his groupies can coo over them and say how much better they are than the official non-Kubrick-Guy ones. Sigh.

Whatever the internal politics, if the code was too complex for the people on the project to write themselves we can’t reasonably expect it to be implemented any time soon (though we may get a couple of nice rounded buttons). Thank goodness for Tiger.

9 Comments »

  1. Odgitfa said

    Woah woah woah woah woah.
    Those are all screenshots? That’s all they’ve done so far?
    That’s really kind of depressing. I can understand how it’s vastly important for a redesign of this magnitude to be fully mapped out, but wouldn’t it have made sense to start integrating even a small section of the framework, bit by bit, as the look developed?

    This is head-shakingly astounding.

  2. Pissed off Joe said

    I look forward to the day when I can, in one stroke, axe that fucking “default blogroll” on my WP blog.

    First of all, it is nothing but forced link whoring to have every WP blog link to Matt, Alex, blah blah blah. I don’t read their sites. Why the hell should they be on my blogroll?

    Second, even if it were, the WP people have been a real pain in the ass by making it excrutiatingly difficult to get rid of all these blogroll-leeches from my site. I can’t just select all of them and delete them in the admin interface. Oh no, I have to delete them one by one. Each time I clicked “delete”, I cursed the WP developers loudly.

    You already have checkboxes; just add a delete button to delete at one shot. Don’t ram your sites down my throat, damn it!

  3. Alan said

    But Joe, how could Matt keep his pagerank if every default install *wasn’t* linking for him? Think of the ego, Joe, won’t somebody please think of the ego?!?!

  4. wank said

    Odgitfa: my guess is that after 18 months trying and failing to reach a consensus, the team were SO DAMN SICK of the thing they didn’t want to spend another second on it. Especially not doing boring stuff like coding. Palm that off on someone who actually likes to code and get back to playing with Photoshop — problem solved.

    Joe: I hear ya. Multiple deletion is the only. good. thing. about links becoming bookmarks in 2.5. In fact, we wordpress.commers already have the power to annihilate multiple links. Mwhahahha!

    Alan: what on earth do you mean? People don’t link to Matt because they’re too lazy or too sheeplike to delete him from their blogrolls! They choose to link him for his lovely egg-yolk-coloured design and scintillating posts about which large corporations are using WP…

  5. Designers design sites with Photoshop mockups… pretty much exclusively, in my experience. I don’t think that anything beyond mockups was really on the agenda for Shuttle. And seeing how they never really finished the project, I’m not surprised that mockups are the end result.

    And some of the design HAS been integrated… a long time ago, actually. The whole blue look of WordPress 2.0 came from Shuttle.

    When did WordPress 2.1 become 2.5?! At this rate, we’ll be at “WordPress CS2” by November.

  6. wank said

    I unofficially declared the next release 2.5 in April, because it was getting unwieldy calling it 2.whatever and 2.1 is blatantly false. I mean, have they ever made a jump of less than .2?

  7. I sort of like the idea of going with “video game sports franchise” or “automobile” versioning. WordPress 2.0 would have been WordPress 2006.

    Of course that system has its own problems with version inflation… you can probably buy “2007” automobiles already.

  8. wank said

    It would be a perfect fit with the release cycle, though, wouldn’t it? The other advantage of using year numbers is that it encourages people to upgrade. If you were using WordPress 2004 it would be obvious that your software was out of date by now, but ‘WordPress 1.2’ doesn’t make that immediately obvious. Though of course there’s the possibility that Windows has got everyone into the habit of disregarding release years (after all, I still use Word 97) and it would have no effect whatsoever.

  9. blaze said

    Haha good point. I thought this to myself but never out loud.

RSS feed for comments on this post · TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s