Design comps have been completed for the Pidgin web site. Due to the time involved, the site will likely need to launch with something similar in look and feel to this, but please post discussions and comments and we'll try to make adjustments as we go.

seanegan: We anticipate launching this Thursday. If we could have these two pages and a "Donate" page for entering credit card information all at least somewhat functional by then, that would be amazing. E-mail me or IM me at seanegan@… if you need anything.

Home Page

​Pidgin Home Page

Notes

• The 'Download Pidgin' link will use javascript to attempt to infer the user's OS and suggest the correct download. In the event that javascript is disabled or the correct OS cannot be determined, the badge will just link to the download section.
• Per the wireframes, several areas have been provided for high-visibility site-wide announcements - this is demonstrated in the header and below the Pidgin.
• The screenshot is a quick toss-in; this will be replaced by a more representative rendering

seanegan: Looks great. With the logo text, and two purple pigeons on the left side, I think it perhaps is a bit too cluttered and off-balance, especially with the two pigeons. Maybe the logo text is a bit too big, also. I would remove the full-body pigeon and either leave that space empty, or perhaps replace him with one of our smileys.

kstange: A friend of mine agrees with this. He suggested moving the Pidgin / download box to the right side to balance it better. I agree the two Pidgins create an unbalanced appearance.

seanegan: I was about to suggest making the "Download" box a speech bubble, potentially coming out of the suggested smiley's mouth, and then looked closely and realized it already was. This should probably be more obviously a speech bubble, or not one at all.

seanegan: I think in general it would be cool if the design featured our protocol, smiley and status icons. They look really great scaled up to web sizes.

seanegan: It would be cool if the page matched the Tango style guidelines (​http://tango.freedesktop.org/Tango_Icon_Theme_Guidelines) the same way that Pidgin does. In particular, the "download" and "learn more" buttons are a bit too shiny.

kstange: If it's possible to detect the browser platform without Javascript, I think it would be better to generate the download box on the server-side, though I'm not sure if the User-Agent would provide enough information. I'm likewise not certain you can tell someone is using Ubuntu/Fedora?/DistroX even if you do use javascript. The arch and platform should be determinable with the User-Agent alone.

seanegan: What difference does it make if it's done client-side or sever-side? I posted a link somewhere in Trac to client-side tricks you can do to see what IM clients are already installed, so that the protocol list can be prioritized. Certainly not crucial, but probably a fun hack.

Interior Page

​Pidgin Interior Page Notes

• The download screen represented in the mock is pulled from the wireframe, and doesn't represent the copy or contents of the download screen. This is just a placeholder to demonstrate the layout of an interior page.

• The left menu demonstrates both selected links (the 'Ubuntu' item is selected) and rollover colors (the 'Red Hat' item is moused over in this example)

seanegan: This looks great!

Other Comments

elb: For the record, I love these pages.

[wiki:seanegan}: In case it wasn't clear, I do too. As does everyone who's commenting. My suggestions are just picking the tiniest of nits. ;) I'm really impressed.