So be this the thread for reviewing and improving some of Bartik's design.
This is sure best done before it gets to core, but as it won't be quick (as mostly) I see no problem in working on it inside core.

Checked out the latest head and played around with the different color schemes, and had a look at the different regions and site components (comments, a.s.o.)
If I had to describe the overall feel of Bartik, would say that it is very puristic and typography driven. It is well done in that respect, and this character should be kept through all modifications IMHO.

The elements that need work IMHO are header, main menu tabs, logo and sidebar blocks.

header
The header is a bit to "Garlandy", with the plain gradient.
Especially when the "featured" region is not there, a lot of emphasis is on the header.

Main Menu Tabs
The tabs for main menu are a bit too generic. Just as the header, they are very prominent.

Logo: Somehow the druplicon does not cut it anymore as a theme logo. It is a tradition worth breaking with. Following this discrussion: http://drupal.org/node/737136#comment-3009488 any logo that looks nice could be used.

sidebar blocks
The sidebar blocks are extremley generic. This becomes especially apparent when one recolors them. I see a problem in the block header being almost the same font size like the block content and hardly standing out at all.

color schemes
the color schemes could be improved a lot, especially by recoloring headers. But I try to stick completely to b/w for the first attempt.

If it is to be b.w., we should maybe have a look at Acquia Prosper and Acqia Slate, that handle the b+w quite well. While Prosper uses a lot of shades of grey, Slate goes more into the pitch dark.
What both of them do is contrast the black and grey with warm colors: the headings in dark red in Prosper and the body background in a brownish-yellowish tone. Prosper uses its logo to attract the eye. Slate has its yellowish headers.

Contrasting some color with else mostly b/w can be done in further iterations.

Theme relies too much on images and the extra regions to make it look nice.
Actually Slate and prosper have a bit of the same problem. But this is a core theme, so we must make it look nice with and without the extra regions.
To make use of the extra regions is hard especially for beginner users, they have to get their head round the block system first, which won't be so quick. As we have no sample content, they won't be pre-filled.

In my first attempt as attached I tried to adress the aforementioned issues. I hope to entice Jen and some more people to have a go at it.

While it may end up in a bikeshed, the areas that need work are very limited, and trying to keep the theme's character this should not go too wild.
Click images for full view.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

eigentor’s picture

Issue tags: +Needs design review

The white area above the header is intentional and meant to give it some air. I tried to cover different use cases with and without special regions activated, or even completely bare bones with just nodes and no images and not even the footer, which might be the most frequent case in out-of-the-box use.

Jeff Burnz’s picture

If theirs one thing that stands out from your designs its the change from tabs to the horizontal main menu - actually I really like this as it gives a strong division between header and page content, and nice contrast to highlight the menu links.

I agree with most all you've said - I do tend to think the default is too dark and a little on the cool side right now - certainly I think Prosper has a better feel in b&w and is well designed in that regard.

For me the default header cannot blend with toolbar, at all, its must have a reasonable level of contrast - however I don't really like the space at the top all that much. Take a look at my screenshot, the shortcuts open/close arrow thing looks weird and floating in space when closed.

Appearance - d7bartik_1276736407828 - toolbar-blending.png

jensimmons’s picture

Category: bug » feature
Status: Active » Closed (won't fix)

I'm not sure what to say in response to this issue. It seems like this is a giant design bikeshed that's been thrown at the project at the last minute.

I am currently working on tweaks to the design, and looking at all of the color schemes (see #762468: Fix up the color schemes for Bartik where, ironically, other people are telling me not to continue working on color schemes — also advice that I don't plan to take).

I am not open to having a community discussion of "design review and improvement proposals." Eigentor has approached me before asking if he can redesign the theme, and I've told him no.

Therefore I am closing this issue.

eigentor’s picture

Jen, I see your point. Still I would not really say "re-design" while I see my proposed changes affect the general feel of the theme too much. I hope to trigger some phantasy and ideas on your side.
Though I see the pain points (logo, header, sidebar blocks with exception of the main menu) were mentioned by yourself als needing improvement.

While design is more difficult to do in a group, as the designers (your) original vision sould be pertained, it could be worth it.
Let's play a little ping-pong.
Your downright closing of the issue is your good right as a module maintainer, but this is not contrib.

I am happy to discuss the single points in sigle issues, so this cannot become too bike-sheddy. But it is _not_ the last minute yet, and if there will be a bikeshed (which is inevitalbe in design stuff in drupal) then shouldn't it be rather today then a week before release?
(remember the discussion about overlay and lots of people complaining this was added without testing)

@Jeff: yes, the space at the top only works if no extra region is there, maybe the idea is not so good.

Jeff Burnz’s picture

I'm with eigentor on this - marking as won't fix is just holding up a process - once this hits core it'll be no holds bared bikesheading and change is just inevitable. The design needs work, lets get on with it.

jensimmons’s picture

No, webchick has been very, very clear, once Bartik is in core, the visual design is locked down.

In fact, she just said:

[4:40pm] webchick: I'm operating under the assumption that we get this in, we have the default theme issue to argue about, there are probably going to be a handful of isssues that come up that just happen when you get a theme in front of a larger audience (e.g. "When I use Chrome 29.003.30.33 on my mom's electronic toaster...")
[4:40pm] webchick: But for the most part, this is done.
[4:40pm] webchick: Put away.
[4:40pm] webchick: We're not doing anymore design
[4:41pm] webchick: We're not doing anymore tweaking of CSS
[4:41pm] webchick: Whatever's getting into core, that's what the D7 version of Bartik looks like.

The time for major design changes was months ago — like February. We are in design-freeze. If you don't want Bartik in core, then make your case to not include it. This project has been 11 months in development. Asking for radical design changes three days before the final patch, or two weeks before the final patch — it's all much too late.

Btw, I fixed the problem shown in #2 above, as promised — in #762468: Fix up the color schemes for Bartik

Jeff Burnz’s picture

Well, yeah, we don't want anything major, but tweaks will be made, just as Seven is being tweaked all the time. I think core inclusion will bring out issues and we'll need to tweak stuff, such as when closer to D7 release and we have a lot more contrib modules to test with, this could highlight things we don't know about yet.

eigentor’s picture

Status: Closed (won't fix) » Needs review
mcrittenden’s picture

Sub (even though it doesn't appear that this is going anywhere based on #6)

Damien Tournoud’s picture

Angie has clarified this in #845742-52: Make Bartik the default core theme. The door is largely open for refinements of Bartik.

eigentor’s picture

O.K., so we best break this up into separate, workable Issues. Still - without giving the impression of a redesign - these pieces need to work as a whole, so complete mockups are needed.

If anyone has visions different from mine, let's have a bit of Design Ping pong. There is a very limited Time Slot for this, but it is right now. Like I wrote, the space over the header is probably a bad idea. Also the Gradients in the sidebar blocks are probably going too far away from Bartiks style, that generally does not use gradients apart from a very soft one from the header.

Let's hit it.

andypost’s picture

Jeff Burnz’s picture

andypost, could you post that as a separate issue, that certainly needs to be looked at.

eigentor’s picture

webchick’s picture

Angie has clarified this in #845742-52: Make Bartik the default core theme. The door is largely open for refinements of Bartik.

Woah. WOAH! No, that is certainly not REMOTELY at all what I said.

I said that the theme has some obvious visual bugs and we need to fix them before release. A whole-sale re-design of Bartik is absolutely not happening.

eigentor’s picture

I hope we won't be up in arms how to define "wholesale redesign". Because the borders are hard to define and very subjective. A little tweak for one person might be a total makeover for another. I can understand Jen having mixed feelings about this to say the least. I in her place would as I would see my vision blurred.

Still the scope of what I am after is pretty much defined in this issue, and yes: the initial mockups in the issue start post change the character of Bartik probably too much. So lets get it closer to the original idea.

jensimmons’s picture

Status: Needs review » Closed (works as designed)