New Pidgin Website

New Website Structure

• Home - Link to download appropriate for detected platform? (like mozilla.com) (nwalp) - That's what Downlaod is. (seanegan)
• Download - Windows installer primary, all others available
• About Pidgin - screenshots, etc.
• Support - Contact, FAQ, docs, etc.
• News - Updates, planet.
• Add-ons - plugins & themes

New Website Home Page

• Logo
• Download button/info
• What is Gaim? intro (a short paragraph - maybe even just a few phrases)
• news/updates
• link to developer site

Global Navigation

Links Required on All Pages

• Home
• Get Pidgin (aka, Download)
• What is Pidgin? (aka, About) - seanegan - I don't think we need this in global navigation. An explanation on the front page should suffice, which a possible "Learn more..." link from there.
• Developers?
• Anything else?
• seanegan: I think a Support page would be useful too. This would cover the FAQ, Bug Reports and Contact Info pages from the Gaim site and should be distinct from the Developer site lschiere: while I think a support page with easy access to submit a bug report and see the FAQ is useful and needed, we do NOT under any circumstances want a forum.

sgarrity: Maybe non-home pages don't actually need any global navigation beyond a link back to the home page.

Sections on old (Gaim) Site

• News - incorporate this directly into the home page - no need for a permanent menu link to it, the end of the home page news can have a link for "old news"
• What is Gaim? - The home page should start this off with a short description and link to a general About Pidgin page
• Documentation - still need this? if so, merge with Support page
• FAQ - Merge with Support page
• Screnshots - Merge with About Pidgin page
• Downloads - Prominent Windows download on home page, link to download page with all other formats
• Windows Port - Does this need it's own page? Is it really a "port'? In a lot of senses it is, there is a lot of win32 specific information on the existing win32 page, and many bugs win32 users report are specific to that platform.
• Plugins - still need this?
• Themes - drop it. Hmmm. we will need something to replace it. developer.pidgin.im's ticket system won't do the job without degrading its usefulness. Similarly we will need something for plugins.
• Bug reports - this is covered by the "developer.pidgin.im" (I disagree, see below --elb) - maybe merge with Support page? --sgarrity
• Project Page - this is covered by the "developer.pidgin.im"
• Contact Info - this is covered by the "developer.pidgin.im"
  • This and bug reports are things that users might not associate with "developer" activities -- they should probably have "user-friendly" (heh) links --elb
  • maybe merge with Support page? --sgarrity
  • That's what I was thinking when I suggested a support page seanegan
  • That sounds great to me, I'm in complete support (pun intended) of that! support.pidgin.im, anyone? Bug reports will probably have to be linked back to developer.pidgin.im in some fashion, but users should be able to find them without thinking "oh, I'm a developer". elb