Differences between revisions 36 and 37
Revision 36 as of 2004-07-10 20:00:14
Size: 6457
Editor: spc1-leed1-4-0-cust194
Comment:
Revision 37 as of 2004-07-11 11:19:12
Size: 7076
Editor: twgate
Comment: just use the wiki?
Deletions are marked like this. Additions are marked like this.
Line 20: Line 20:
Line 101: Line 100:
= Comments =
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 Front``Page.

At the [http://moinmoin.wikiwikiweb.de/ moinmoin homepage], we are doing ''everything'' in the wiki. It works ;)

-- ThomasWaldmann [[DateTime(2004-07-11T11:19:12Z)]]

Why?

During PyCon 2003 the need to make changes to python.org was clearly identified. See PythonOrgWebsiteRedesignOpenSpace.

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.

Phase 1

Primary goal is to quickly improve the site's basic usability:

  • Reduce some of the duplication (Summary vs. Intros, Events.html vs /conferences/)
  • 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.)
  • Fix the egregiously bad/outdated parts (the FAQ) (in progress)
  • Simplified search on front page

Phase 2

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

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

Mailing List

IRC session

An IRC session took place between 18:00 and 17:30. Logs available here :[http://www.pollenation.net/assets/public/pydotorg-redesign/irclog210703.html html formatted] [http://www.pollenation.net/assets/public/pydotorg-redesign/irclog210703.txt raw] In attendence were Kevin Altis, Tim Parkin, Matt Goodall, and Fred Drake.

Latest IRC Session jun 2004 [http://www.pollenation.net/assets/public/pydotorg-redesign/FreeNode-psfprc.log psfprc]

Python logo images

Other tasks

  • Getting rid of PSA stuff and moving still-valid info to other parts of the site.
  • Reorganizing [http://www.python.org/UserGroups.html UserGroups] and [http://www.python.org/doc/NonEnglish.html NonEnglish] -- there's currently a lot of overlap, and what I'd really like to do is move it to a database with multiple views

  • 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 [http://ht2html.sourceforge.net/ 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.

Comments

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 [http://moinmoin.wikiwikiweb.de/ moinmoin homepage], we are doing everything in the wiki. It works ;)

-- ThomasWaldmann DateTime(2004-07-11T11:19:12Z)


CategoryPythonWebsite

PydotorgRedesign (last edited 2008-11-15 14:00:16 by localhost)

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