Note: Much of this has been done. See PythonWebsite for ongoing work on content and tools for the python.org website.
The overhaul is taking place in (at least) two phases, as detailed below. The phases are not set in stone, items can and should be moved around as necessary.
Primary goal is to quickly improve the site's basic usability:
- Reduce some of the duplication (Summary vs. Intros, Events.html vs /conferences/) (Done, pretty much)
- Improve usability from the standpoint of very inexperienced people who get directed to python.org. (The site is probably OK for experienced users.)
- Improve usability of the exceedingly busy top page. If a new graphic design is necessary to get that done, so be it. (Some simplification has been made, but it's still awfully crowded.)
- Fix the egregiously bad/outdated parts (the FAQ) (done)
- Simplified search on front page (done)
Currently, it is largely unknown what will happen during this phase but here are some possibilities:
- Complete redesign of the site including graphic design, structure and navigation. The focus should be on making the site more obvious to use (particularly for beginners), make it look more "professional".
- Content management to reduce the load on the webmasters. (Site mirroring needs to be seriously considered.)
- User comments for documentation.
Home Page Mockups
Mockups from Pollenation A web design & development company from Yorkshire, the spiritual home of 'Monty Python', allegedly
- Mockups from Walter
Home Page must haves
Feel free to expand this, I just want to get down my priorities. Based on the stats, feedback at OSCON, and my own usage of python.org. The home page has a few very clear usage scenarios.
- Someone knows nothing about Python, so the home page has to make it clear without a lot of extra navigation
- A new or existing user needs to download Python (most typically the current version)
- Documentation, documentation, documentation !
- Related to documentation is the need to search the current documentation and/or site
- Then there are a whole host of other things to do
Other home pages for consideration
Latest IRC Session jun 2004 psfprc
Python logo images
- Getting rid of PSA stuff and moving still-valid info to other parts of the site.
(Done -- see http://www.python.org/community/ . Must now update links.]
- Figuring out how to manage the commercial exits and other kinds of links to external resources
- Fixing up the pycon directory (I made a boo-boo when setting it up, and we'll need to move the old stuff before starting in on DC2004) (Done).
Reorganizing Intros and Newbies -- also a lot of overlap. (Done -- see http://www.python.org/topics/learn/ . Must now update links.]
Implement a well-formedness checker for HT2HTML, to help support well-formed XHTML on the site (Fred Drake volunteers). A simple version of this now exists and can be accessed via make wfcheck in a pydotorg checkout, but the output isn't as helpful as it could be. Most pages don't pass the check.
How about simply upgrading the python.org wiki and making more use of it?
Using a wiki makes it much easier to update content (as you see right here), add links and fix stuff. It puts the burden of maintaining the site on the shoulders of the community, not a few webmasters. The current MoinMoin version (not the old version you are using now) is themeable and has access control lists for critical pages, like the FrontPage.
At the moinmoin homepage, we are doing everything in the wiki. It works
-- ThomasWaldmann 2004-07-11 11:19:12
Rewriting more of our content from HTML into ReST will help with well-formedness, and that's probably easier than fixing the HTML page-by-page.