| Version 8 (modified by , 17 years ago) (diff) |
|---|
Pidgin Site Wireframes
Blend Interactive has generated a set of wireframes for the new site. Please have a look and make some comments here to help guide us in the right direction.
The purpose of the wireframe stage is to consider the structure and content of the site without any consideration for design; once we've reached some rough consensus on the contents, we can get the designers involved in creating the actual look and feel. At this point we're focusing on where to put things, and why to put them there.
I've broken the wireframe document up into sections below, but here's the whole document if that's easier to read.
User Groups
Questions
- Do these groups accurately represent the expected audience of the site?
- Is there anything that should be added to this list?
- Other questions/comments?
Site Map
Questions
- Anything else that should be added to the site map?
- Other questions/comments?
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.
Home Page
Home Page Wireframe and Notes
Questions
- What's the best way to describe Pidgin in the shortest amount of text? We want to tell people what Pidgin is in a compelling way in as few words as possible. (Users will often gloss over long descriptions).
- Any good taglines for Pidgin?
- Other questions/comments?
Download Section
Download Section Wireframe and Notes
Questions
- What types of packages and binaries will be provided for Pidgin?
LSchiere?: The downloads section also looks good. I'm not sure we would have much in the way of alternates though beyond the source itself. We typically have a collection of rpms, the source in .tar.gz and .tar.bz2, 3 win32 installers (with gtk, without gtk, and debug), and sometimes an autopackage. We have not distributed debs ourselves in the past, mostly because the debian developers have done an excellent job providing packages for unstable.
- Will there be repositories for systems like yum and apt?
LSchiere?: I had not considered this. I think I'm a fan of the idea though.
- Are there volunteers available to maintain installation instructions for their favorite distros?
LSchiere?: We have some notes, particularly about getting ssl/tls to work with gaim on various distros. In the past, there have been some patches providing additional information for various distros, but not much.
- Other questions/comments?
About Section
About Section Wireframe and Notes
Questions
- What are the features of Pidgin that should be highlighted to prospective users?
LSchiere?: the status stuff needs a section either here or in support.
- Should the official organization (IMF) that's now behind Pidgin be explained?
- Where and how can we explain that Pidgin was formerly Gaim, and the reasons for the change?
- Other questions/comments?
Support Landing Page
Questions
- What are all of the support resources that are available to users having problems?
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?
Bug Report
Bug Report Wireframe and Notes
Questions
- Does this seem like a good method to handle bug reports?
LSchiere?: this is utterly awesome.
- Any other resources that should be searched for solutions?
- Other questions/comments?
Contribute Section
Contribute Section Wireframe and Notes
Questions
- Are there any other ways to contribute that should be highlighted?
LSchiere?: we are going to be using monotone, 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.
- Other questions/comments?
News Section
News Section Wireframe and Notes
Questions
- Should the 'official' news remain separate from the blogs?
LSchiere?: I expect official news would remain separate yes.
- Should we attach author names to official posts?
- Other questions/comments?
