Changes between Version 13 and Version 14 of WebsiteWireframes

Timestamp:

Jan 18, 2007, 10:53:49 PM (17 years ago)

Author:

joekepley

Comment:

--

WebsiteWireframes

@@ -30 +30 @@
 
 >>[wiki:lschiere]: In your site map, you have a section for developer blogs in both "About" and "latest news." Do we want this duplication?
->joekepley: I was thinking of the Team page in the about section as something more akin to the 'contact info' page on the current site, perhaps with a bit more bio information. The 'Dev Blogs' page would be more like the current 'planet' site - an aggregation of articles from developers' blogs. So I don't think the duplication is a big deal. In one case it's part of the contact info, and in the other it's there to provide context to the posts.
+>[wiki:joekepley]: I was thinking of the Team page in the about section as something more akin to the 'contact info' page on the current site, perhaps with a bit more bio information. The 'Dev Blogs' page would be more like the current 'planet' site - an aggregation of articles from developers' blogs. So I don't think the duplication is a big deal. In one case it's part of the contact info, and in the other it's there to provide context to the posts.
 
 ----
@@ -44 +44 @@
  * Any good taglines for Pidgin?
 > Gaim's tagline is "The Penguin Pimpin' IM client that's good for the soul." I don't know if Pidgin has/needs/wants a tagline ;)
+
  * Other questions/comments?
-> [wiki:sgarrity]: "The current site has "A multi-protocol instant messaging (IM) client" - Not too exciting, but it works.
+>> [wiki:sgarrity]: "The current site has "A multi-protocol instant messaging (IM) client" - Not too exciting, but it works.
+> [wiki:joekepley]: I kept the 'multi-protocol IM client' bit as the start of the description. "multi-protocol" is a bit technical, but I couldn't think of anything simpler without being confusing. 
 
 > [wiki:seanegan]: It would be fun to change the screenshot on a very regular basis. The silhouette is obviously of the buddy list and a conversation window. It would be fun to be able to change the conversation text frequently to in-jokes/obscure 80s pop culture references/current events. Clearly not a huge priority.
 
->[wiki:seanegan]: It might be nice to have the full text of the latest news post on there instead of just a headline.
+>>[wiki:seanegan]: It might be nice to have the full text of the latest news post on there instead of just a headline.
+> [wiki:joekepley]: I had the full text on there, actually, and pulled it at the last minute in order to keep the visual focus on the download and 'about' elements. We can add it back in and just make sure we focus things properly in the design.
 ----
 
@@ -70 +73 @@
 
  * Other questions/comments?
->[wiki:seanegan]: Where does the user actually click to download the package? Is it possible to download the package directly from the homepage, or do you have to go to this page first? From this page, where is the link to download? For UNIX distros, it would be nice if the home page contained two links, one for the binaries and one for the source... but in a way not to confuse the 15 year old Ubuntu livecd users. ;)
+>>[wiki:seanegan]: Where does the user actually click to download the package? Is it possible to download the package directly from the homepage, or do you have to go to this page first? From this page, where is the link to download? For UNIX distros, it would be nice if the home page contained two links, one for the binaries and one for the source... but in a way not to confuse the 15 year old Ubuntu livecd users. ;)
+>[wiki:joekepley]: For the example page I drew up in the wireframe, the idea was that we had a repository that Ubuntu people should use instead of downloading the tarball; My plan was to explain the recommended install method for each distro in the (2) area, then alternates in the (4) area. So if, say, it's the Windows page, then there would be a big download link there to the installer exe. But if it's a Linux install that already has the latest Pidgin in the distro (or there's a repository provided), then the user should install through those methods unless they have a good reason not to. The sourceforge files page is pretty confusing to 
+those 15 yo livecd users because it's not obvious what the smartest install option is. 
 ----
 
@@ -80 +85 @@
 
  * What are the features of Pidgin that should be highlighted to prospective users?
->>[wiki:lschiere]: the status stuff needs a section either here or in support.
->[wiki:seanegan]: The screenshots on our current screenshot page are dated, but are a good start. Something like NetworkManager integration probably isn't too good because it's not visual, but there are plenty of UI things to show off.
+>>>[wiki:lschiere]: the status stuff needs a section either here or in support.
+>>[wiki:seanegan]: The screenshots on our current screenshot page are dated, but are a good start. Something like NetworkManager integration probably isn't too good 
+because it's not visual, but there are plenty of UI things to show off.
+>[wiki:joekepley]: Agreed on the NetworkManager thing. I just needed a feature to mock up, you had made a recent blog post on it, and I thought it was cool. :-)
+
  * Should the official organization (IMF) that's now behind Pidgin be explained?
 >[wiki:seanegan]: This should probably just be a link to [imfreedom.org], which would just be a simple static HTML page with everything we need to disclose.
+
  * Where and how can we explain that Pidgin was formerly Gaim, and the reasons for the change?
->[wiki:seanegan]: Luke asked if the settlement even allows us to mention this. I think it does; it says we can use Gaim as it refers to "it's past use as a technical term" or some such. In either case, I don't expect any resistance from AOL about doing this. That said, I think the best place would be on the homepage, in the description (labeled 4) and in one of the transient areas. We would then phase these out over a couple of months. Perhaps phase out the alert after a week or so, and the description later. This would ease the initial confusion of people getting redirected from gaim.sf.net.
+>>[wiki:seanegan]: Luke asked if the settlement even allows us to mention this. I think it does; it says we can use Gaim as it refers to "it's past use as a technical term" or some such. In either case, I don't expect any resistance from AOL about doing this. That said, I think the best place would be on the homepage, in the description (labeled 4) and in one of the transient areas. We would then phase these out over a couple of months. Perhaps phase out the alert after a week or so, and the description later. This would ease the initial confusion of people getting redirected from gaim.sf.net.
+>[wiki:joekepley]: Could we add something to the description? Maybe "Pidgin (formerly known as Gaim) is a multi-protocol IM client..."
+
  * Other questions/comments?
->[wiki:seanegan]: It would be great if selecting screenshots refreshed on the page without a reload.
+>>[wiki:seanegan]: It would be great if selecting screenshots refreshed on the page without a reload.
+>[wiki:joekepley]: You read my mind. I'm thinking that this section could get a little [http://script.aculo.us scriptaculous] love.
 
 ----
@@ -98 +110 @@
 
  * What are all of the support resources that are available to users having problems?
->[wiki:lschiere]: there are definitely going to be mailing lists, and a FAQ.  The wiki here at developer.pidgin.im will also have information on figuring out what is going wrong.  My hope is to have pages here that are useful to users, but which can help point users interested in doing more in the right direction towards submitting a patch.  In the past, we have written various page length articles on various things, protocol descriptions, things like our reaction to skins, plain text passwords, so on.  These could remain static pages, or could be pages here with links to them from a Documentation page.  I do not know which approach is best.  A good search would be awesome regardless.
+>>[wiki:lschiere]: there are definitely going to be mailing lists, and a FAQ.  The wiki here at developer.pidgin.im will also have information on figuring out what is going wrong.  My hope is to have pages here that are useful to users, but which can help point users interested in doing more in the right direction towards submitting a patch.  In the past, we have written various page length articles on various things, protocol descriptions, things like our reaction to skins, plain text passwords, so on.  These could remain static pages, or could be pages here with links to them from a Documentation page.  I do not know which approach is best.  A good search would be awesome regardless.
  * What else should be added to the Support section?
  * Other questions/comments?
@@ -125 +137 @@
 
  * Are there any other ways to contribute that should be highlighted?
->>>[wiki:lschiere]: we are going to be using monotone, [wiki:elb] had mentioned that it might be worthwhile to have a snapshot of the monotone database posted in an automated fashion so that those interested in contributing can get a jump start, rather than the half-hour to an hour initial monotone checkout.  I do not know how hard/easy it would be to do this.
->> [wiki:elb] The generation of the database itself is trivial; mtn pull to an existing, dedicated database to update it (which takes care of not having to lock anything), copy it alongside the current download database, and mv it overtop.  A new version will be atomically available to fresh downloaders.
->[wiki:seanegan]: That would live within developer.pidgin.im, not on this page. A lot of people have asked if we have "buttons" that they could include on their webpage. Perhaps this sort of thing could be considered a form of contribution.
+>>>>[wiki:lschiere]: we are going to be using monotone, [wiki:elb] had mentioned that it might be worthwhile to have a snapshot of the monotone database posted in an automated fashion so that those interested in contributing can get a jump start, rather than the half-hour to an hour initial monotone checkout.  I do not know how hard/easy it would be to do this.
+>>> [wiki:elb] The generation of the database itself is trivial; mtn pull to an existing, dedicated database to update it (which takes care of not having to lock anything), copy it alongside the current download database, and mv it overtop.  A new version will be atomically available to fresh downloaders.
+>>[wiki:seanegan]: That would live within developer.pidgin.im, not on this page. A lot of people have asked if we have "buttons" that they could include on their webpage. Perhaps this sort of thing could be considered a form of contribution.
+>[wiki:joekepley]: Good idea on the buttons. We can add verbiage and a page for it. With regards to the dev snapshot, we could provide links to the useful bits for new developers in the wiki from the developer page on the site. A quick howto for compiling and developing with pidgin would be great. I tried to run a build off of a recent nightly and failed miserably (but I'm pretty dense so that may not say much).
+
  * Other questions/comments?