[Pidgin] #2012: I am sorry, but your Website sucks.

[Pidgin]

#2012: I am sorry, but your Website sucks.
----------------------+-----------------------------------------------------
  Reporter:  blubb0r  |       Owner:                      
      Type:  defect   |      Status:  new                 
  Priority:  minor    |   Milestone:                      
 Component:  webpage  |     Version:  2.0.2               
Resolution:           |    Keywords:  Pidgin website sucks
   Pending:  0        |  
----------------------+-----------------------------------------------------
Comment (by rekkanoryo):

 I am slowly working on migrating content from our old site to this wiki.
 I simply have not had the necessary time to think the structure through
 properly.  I have a few ideas that are somewhat in line with the
 suggestions here that I will try to implement as my time and patience for
 wiki editing allows:
   * Move the existing smiley themes stuff to !SmileyThemesHowTo (which, of
 course, does not yet exist) and use SmileyThemes to explain what they are.
 Make a blatantly obvious link from WikiStart to the SmileyThemes page.  On
 the SmileyThemes page, provide a table with links to some popular smiley
 themes.  This part may prove difficult, as I've never cared to search for
 additional themes once I found "exhaustive" ages ago, so I have no clue
 what is popular and what isn't.
   * Create a Plugins page, linked quite conspicuously from the FAQ and
 from WikiStart.  On this page explain the concept of plugins, explain that
 we don't support any of the plugins that are listed on the page, and then
 provide a table that developers/users can edit to include their own
 plugins.  Of course this page would include the Plugin Pack, since I'm a
 developer there (gotta plug my own stuff, you know!).
   * A !PluginHowTo page linked quite conspicuously from the FAQ, the
 Plugins page, and also WikiStart (under the developers section).  Of
 course, include additional linkage as required.  Granted, this will need a
 lot of maintenance, but the painstaking maintenance should only be
 necessary at major version changes.  Link quite obviously to the API
 reference.  Explain plugin ID's similarly to the doxygen doc on the
 subject (the plan here is to supersede the stuff in doxygen and make it
 more easily visible to those seeking it), but try to expand on it where
 possible or feasible.  Flog the dead horse some more on the differences
 between a core/libpurple plugin, a protocol plugin, a loader plugin, and a
 Pidgin or Finch (a.k.a. UI) plugin.
   * Any other random work-inventing ideas that occur to me later.
 Don't expect this stuff overnight, though, folks.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/2012#comment:6>
Pidgin <http://pidgin.im>
Pidgin