3.2 feature freeze is this weekend, with…

3.2 feature freeze is this weekend, with final post-testing/usability review UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. freeze about a week later, and betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. starting on May 11. With this tight of a timeline, it’s entirely likely that it is too late to do a style update for this release, and it will wind up in 3.3. That said, sometimes everything just comes together in a perfect storm of creativity and collaboration, and things can happen faster than normally are possible. Maybe this will be one of those times.

Just over a week ago, I was talking with Matt, and we were discussing two things:
1. What’s the UI equivalent of the performance improvements that are forming the bulk of the 3.2 release.
2. Every platform and its brother seems to have copied the WordPress admin UI, and what was once lauded as amazing and a huge step forward is now kind of looking like everything else (through no fault of our own, other than the ‘fault’ of being awesome). Maybe it’s time for us to update the style a little bit and start the next wave.

To that end, I posted here on April 20 posing the question, “What if?” regarding our admin styles, making it clear I was not talking about a structural redesign, but a style update. @chexee did a comp. I made a comment. @ryanimel did a follow-up comp. Collaboration in action!

Since @chexee is entering her exam period (graduation soon, yay!), I asked Ryan if he’d like to do another iteration combining some menu styling updates, and he said yes (new contributor, yay!). I sent him a PSD of the menu/headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. refresh that we talked about doing back in 2.8 but decided to put off until later, then wound up never doing. It was after 10pm when this went down last night, so I dusted off photoshop and did some comp combining of my own in case Ryan wound up not having time. I emailed the resulting comp as a POC to the lead and commit-level developers (including Matt) to get a gut check on if this was something we wanted to pursue. Yes.

But! It’s much too late for 3.2. Or is it? If the styling changes are mostly happening in CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. and someone volunteers to work on it, then maybe not. Here’s where it stands:

  • Chelsea did the first comp in response to my post.
  • Ryan Imel did the second comp in response to my comment on Chelsea’s comp.
  • I sent Ryan Imel PSD of Matt Thomas’s nav/header refresh comp from 2.8
  • I cut and pasted bits of Ryan’s comp and MT’s comp, and moved some stuff around to make a new comp. Sent to leads for review.
  • Leads liked it. Talked about what I would change if spending actual time on it. Got some feedback for what we need to address/finish/improve for it to be coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-acceptable.
  • Talked to MT about addressing several issues, since menu/header stuff came from his comp. He’s going to try to do several things today, including *Create a gutter between nav sections, *Change direction of arrow so it goes from menu to main area, *Try a repositioning of header elements so that blog title and screen could be oriented in a navigational breadcrumb (involves smaller font, typography adjustments), tabs could flip up again, smaller footprint for header, bring back faves menu (probably need to wait unti l3.3 to talk about removing it). He’ll also take a stab at giving a little gradient and/or bevel love to the boxes to keep the crisp edges and feeling of depth while making it less like 90s windows ui (requested in feedback). It anyone else would like to take a stab at this as well, if you can do it by EOD today, have at it and we can look at it along with MT’s and see what looks like it fits best.
  • Need a volunteer to jump in on CSS updates for it.
  • @azaozz will check into the JS implications.
  • Need to get a patch of general intent into core by end of tomorrow, to meet feature freeze. We then have until May 11 for UI refinements. So please, let’s not start a conversation in this thread about details. We have all next week for that, and can devote the UI meeting to it as well. Let’s talk details after we have a basic something done that gets in by freeze. If we don’t get a first pass in by freeze, then this will be postponed until 3.3, so please keep remarks focused.
  • Once initial patch goes in, we can delve into ui details/improvements. Will also start a ticket for some text improvements, which everyone can contribute to as well.

What is cool about this is that even something happening quickly already has 4 different people contributing to the design to get it to where it ought to go.

#css, #dashboard-2, #style