Design Initiative Wireframes

@2 - I looked at them ages ago and to be frank they don't really suit our purpose, however I think the list of elements they put together is spot on. What I do like about C3's wires is that they're kind of simple, and what I have been working on is probably overly complex - need to find some middle ground.

@animelion - this one is done in Photoshop, actually normally I would use Fireworks, but for some crazy reason I just decided to use PS. I'm updating this all the time and mortendk is working on some stuff also. I think we'll end up having multiple wireframes and designers will be able to choose which one they want to use (if anything at all, they're only guides so if you choose not to use them thats up to you).

We'll be discussing these wireframes in next weeks IRC meeting: http://groups.drupal.org/node/159124 so that would be a good place to fire around questions.

@Jacine, under the articles group there is a book page, but I have not yet added a user profile or those other important things like aggregator stuff.

I actually deliberately left out the shortcuts link because it might be going away in D8 #1164782: The icon to add something to shortcuts wasn't clearly discoverable., that said I think we should add it in regardless, since its currently part of the UI atm.

There are some tabs in there but they are badly done, on the search results page, I need to clean these up (any help appreciated!).

There's an action link on the Forums page, this is the sort of thing we need to explain a bit more about - which is why I want to send an annotated PDF or use Notable to give more information about these UI elements.

Regarding flexibility - unrestricted IMO. Total freedom - I personally want to see where designers take Drupal. I think if we start placing restrictions we might limit outside-the-drupal-square thinking, which is what i want to avoid.

I am used to building and theming off of wireframes, so it's just something I'm conditioned to think. I'm probably not the only one though.

Yes, totally agree with that sentiment - we have to be shouting loud and hard that designers do not have to follow these wireframes and they are merely a guide to Drupal output. Maybe we need to think up a better name than "wireframes" since that name carries the connotations you speak of.

The amendments to the portfolio are good, I can roll that in.

What I really want to do is get rid of about the half the screens (if possible) so start to combine stuff and cut down on the bloat in the PSD, its getting massive and quite complicated - and clearly easy to miss stuff, which I was worried about.

@dodazzi - we could provide HTML wireframes in addition to the graphical wireframes. What do you think would be the main purpose of having HTML wireframes (I ask because I hardly ever use them - I tend to go strait from PSD to Drupal).

Should be easy to submit - just add as a zip archive + a some screen shots. I can't say that I'm terribly excited about this option - main reason is that an HTML wireframe should ideally be very close to what the theme will actually be like under the hood i.e. responsive/adaptive framework, mobile first (maybe) and so on - and we haven't really even started on those conversations with any depth. So my main question is - can we get that done by mid August?