Patch for header updates I've been working on with Jane today. Smaller site title, larger page title, adjusted style for user-info dropdown, new add-new-h2 style, and removed button class from all add-new-h2 links.

Arrows for toggling menu items and postboxes don't change cursor to show it's clickable (menu one looks on purpose, what's the reasoning on not showing it's clickable)? -- I can do a quick patch, just wanted to know why it was done on purpose.

Arrow on post box is aligned weird (too far to left or close to the border)? Just saw Mark posted this as well

Just a reminder to contributors that this patch went in without being "finished," so it might be worth waiting a day for Daryl to finish getting things put in before listing small details. We went with the broad stroke for v1 to get it up there so people could see progress, but have a whole bunch of stuff to finish up before we start debating details.

I made ​a thread on UI blog for people to make UI suggestions, ask questions, debate colors, positioning, size, etc. related to this ticket. This way, we can keep the ticket relatively clean for tasks that need to be completed that have been approved by leads, and/or for reporting bugs with the new code. Thanks.

Would there be any support for the core team for a way to disable the redundant submenu page link via a hook?

Lets get the UI refresh finalised before getting into adding hooks for things

I asked the question to determine if it was worth the effort to submit another ticket for a hook; an opinion that it might be considered would not block UI refreshing in any way that I can see. A simple "yes", "no" or even "maybe" would suffice.

I've been following along with Daryl's changes and applying the changes to the Blue Admin. (colors-classic.dev.css) I've attached a diff (blue_update.patch) of what I've modified so far. The colors-fresh.dev.css and the colors-classic.dev.css now match line-for line. There is still more tweaking to be done with colors/borders/menus/widgets. I will post up for a review on the blue changes on make.wordpress.org/ui after the grey is set in stone. So, as we go along, I'll be replacing the patch with modifications following daryl's modifications.

That's a very rough beginning toward moving what is now in the first h2 of each screen up into the h1. The blog name is now moved over under the Howdy. set_screen_attribute() allows setting the title, sub_title, icon class, and other bits for the current screen. Plugins can use this off of a load-* hook.

Regarding the Screen Options and Help dropdowns, it might be useful to add a "close" link to the top right of those sections. As it is now, you have to move the mouse quite a bit to close those sections, especially if the screen is very long.

If the screen_icon size change is staying is the plan to change the screen_icon class to icon28 instead of icon32? That way plugins could provide icons for both 3.2 and pre 3.2. Or is that being accounted for some other way?

Patch for header updates I've been working on with Jane today. Smaller site title, larger page title, adjusted style for user-info dropdown, new add-new-h2 style, and removed button class from all add-new-h2 links.

I can't get a screenshot to show the cursor, but in [17861], the three boxes on the Add/Edit Links page Name, Web Address, and Description show the move cursor even though those three boxes are not moveable. The code responsible is:

Attached a patch to update the top right drop-down menu in Blue. This patch also ports over color styles from nav-menu.css over to colors-fresh.css and colors-classic.css. Still some color modifications left to do in colors-classic.css on the menus. Also, cleaned up the formatting of nav-menus.css a bit while I was at it.

li.wp-menu-separator still contains an anchor tag ( a.seprarator ) that targets ?unfoldmenu=1 resulting in a page reload. The cursor no longer changes to the '➞' or '←' types, indicating that you can fold/unfold anymore, so do these still need to be links? I love being subscribed to this thread <3

I would rather leave it as cursor:default; but make the arrow go darker on hover. In all browsers the pointer is used for links, the arrow (default) cursor is used for controls and all default controls (look at the Submit button below) have hover effect.

cursor: pointer; makes more sense to me, which is why I posted the other ticket. A change to a darker color could work, but it just needs to be consistent. I think the way it works on the widget screen, as scribu pointed out, is great. I think all postboxes should act the same way.