Differences between revisions 12 and 17 (spanning 5 versions)
Revision 12 as of 2003-10-07 03:22:21
Size: 1977
Editor: MikeRovner
Comment:
Revision 17 as of 2009-09-21 08:57:36
Size: 1788
Editor: techtonik
Comment: make site work more fun
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
This page collects suggestions for improving the python.org web site.  Perhaps we'll
manage to implement some of them at PyCon?
This page collects suggestions for improving the python.org web site.
Line 4: Line 3:
Aahz:
    * I've been thinking (without much energy to do it) that the
    Community link on the main page ought to point at a new page instead
    of the incredibly stale PSA link. ''Well, PyCon will be a focal point
    for whatever replaced it, I'm guessing - SH''
'''improving''' means enhancing site user's experience to find information faster and easier using the way they've used to. Major things that need improvement are usually obvious for everybody, but they seem Epic (Single Sign On, OpenID, online docs editor). Minor features are on the surface for each of us in particular, but they are not obvious for everyone else (wiki page subscription on edit, boring design).
Line 10: Line 5:
    * While doing that re-org, perhaps the SIGs link ought to be moved
    and the Beginner's link replace it, with a prominent link on the
    Newbies page to "What is Python?"
'''improving''' is a process. Key to make any process effective is to provide a '''feedback''' that should be easy to reach and visible to others (see PHP online manual comments).
Line 14: Line 7:
    * HOW-TOs currently at http://www.amk.ca/python/howto/ should be
    moved to http://www.python.org/ (somewhere)
A lot of information causes frustration. That's why ''twitter'' takes over ''blogger''. Too much '''inventory''' in the room makes it hard to navigate and hard to notice needed things. '''cleanup''' should throw unused stuff from standing in the way. It's especially true for wiki, but various python.org pages are accounted as well. Big amount of information reduces ''fun factor''. Separate '''status''' page will help people see what's going on and have more fun by focusing their work and working together.
Line 17: Line 9:
    * http://www.python.org/doc/Summary.html needs an update  * http://www.python.org/Jobs.html should be moved to a database with a secure and user-friendly front-end. (Wikis won't do it for many people we're targeting.)
Line 19: Line 11:
    * http://www.python.org/psa/Users.html should be moved to a Wiki == Wiki ==
 * Add "automatically subscribe to pages I edit" plugin from http://moinmo.in/MoinMoinPatch/AutomaticSubscriptionOnEditPreference to increase people awareness about changes that going on on the wiki.
Line 21: Line 14:
    * http://www.python.org/Jobs.html should be moved to a database with
    a secure and user-friendly front-end. (Wikis won't do it for many
    people we're targeting.)
 * Fix bug with PythonAroundTheWorld not appearing in CategoryAroundTheWorld (may have something to do with http://moinmo.in/HelpOnCategories)
Line 25: Line 16:
    * http://www.python.org/doc/NonEnglish.html and
    http://www.python.org/UserGroups.html need to be re-organized,
    probably using a database so we can create multiple views.

AMK:
 * Suggested top links, in this order: "Home", "About", "Download", "Documentation", "Help", "Search". That's 7 links, not 8; any suggestions for one more? ''A random choice made once an hour from a given set? Advertising? Python tips?''

 * The top page is too long. Ideas to shorten it? ''One suggestion might be to put the text of the Google quote next to the graphic. For example, [http://www.holdenweb.com/Python/python.org.htm] gets more directly to the point.''

 * doc/Intros.html: why two "What is Python?" links? ''For the especially clueless? :-)''

 * Too many introductions! doc/Intros.html, doc/Introduction.html, doc/Newbies.html, doc/Hints.html. Trim down this material and have one location for it.
 * Update wiki SystemInfo to latest version

This page collects suggestions for improving the python.org web site.

improving means enhancing site user's experience to find information faster and easier using the way they've used to. Major things that need improvement are usually obvious for everybody, but they seem Epic (Single Sign On, OpenID, online docs editor). Minor features are on the surface for each of us in particular, but they are not obvious for everyone else (wiki page subscription on edit, boring design).

improving is a process. Key to make any process effective is to provide a feedback that should be easy to reach and visible to others (see PHP online manual comments).

A lot of information causes frustration. That's why twitter takes over blogger. Too much inventory in the room makes it hard to navigate and hard to notice needed things. cleanup should throw unused stuff from standing in the way. It's especially true for wiki, but various python.org pages are accounted as well. Big amount of information reduces fun factor. Separate status page will help people see what's going on and have more fun by focusing their work and working together.

  • http://www.python.org/Jobs.html should be moved to a database with a secure and user-friendly front-end. (Wikis won't do it for many people we're targeting.)

Wiki


CategoryPythonWebsite

SiteImprovements (last edited 2020-07-04 14:12:28 by ChrisM)

Unable to edit the page? See the FrontPage for instructions.