Differences between revisions 33 and 34
Revision 33 as of 2010-03-15 14:54:10
Size: 3734
Editor: techtonik
Comment: turn off captcha
Revision 34 as of 2010-03-15 15:00:33
Size: 3818
Editor: techtonik
Comment: trac wiki syntax is more intuitive and familiar to developers
Deletions are marked like this. Additions are marked like this.
Line 24: Line 24:
 * Add autolinking to python tracker, e.g. issue #1024, issue 1024, bug 1024 and bug #123  * Add autolinking to python tracker, e.g. issue #1024, issue 1024, issue1024, bug 1024 and bug #123
Line 54: Line 54:
 * Switch to [http://trac.edgewall.org/wiki/MoinMoin|TracWiki syntax]

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.





SiteImprovements (last edited 2019-10-27 00:14:39 by JennyRyan)

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