[Pydotorg-redesign] What are the goals?

[Fred L. Drake, Jr.]

Roy Smith writes:
 > Again, I'm with Skip.  I can't remember the last time I actually used a 
 > computer that didn't support some kind of graphical environment, but 
 > it's fairly common that I've got a slow network between me and a remote 
 > Unix box I'm working on.  If I've got to download something from a web 

I just poked at the current python.org with "links" (different from
"lynx", at least in that it happened to be installed on this box), and
the site held up fairly well; the organization was still sloppy, but
the presentation degraded cleanly and was about as usable it is on the
recent versions of Mozilla I'm accustomed to using.

That's the kind of behavior I'd like to see on the new design.  I'm
not concerned with seeing the exact same thing on every browser.  I'd
like the site to be navigable on NS4, but degraded presentation is
quite tolerable.  (Heck, it's almost desirable to get NS4 users out of
their slump!)  If we can do it using a simple stylesheet with an
@import to load portions of the style that would break NS4, that seems
like the right level of effort.  Making a dynamic selection on the
server seems like the wrong approach, and doesn't lend itself to
mirroring this site; @import takes care of that quite nicely.

 > > Like it or not, CSS is the future.
...
 > Once again, Skip I agree with Skip.  I'm not particularly thrilled with 
 > CSS, but the fact is it's the standard, it's here to stay, and it's 
 > supported in all mainstream browsers.  To talk of putting effort into 
 > NS4 while ignoring CSS is lunacy (IMHO).

Whatever the faults of CSS, it's much better than having the style
information inline.  That's good enough for me.  We're not getting
beyond it for quite a while.


  -Fred

-- 
Fred L. Drake, Jr.  <fdrake at acm.org>
PythonLabs at Zope Corporation