Discussion:
[Pydotorg-redesign] RE: [marketing-python] Zope and python.org re-design
Kevin Altis
2003-08-09 17:06:39 UTC
Permalink
From: Roy Smith
As a totally unscientific survey, I just looked at a few
language-specific web sites and evaluated them according to my own
TCL (http://www.tcl.tk/). I like it. Looks professional without being
too glitzy.
This is way too busy for me.
Ruby (http://www.ruby-lang.org/en/). Neat and clean, but sort of ugly.
Too monochromatic.
Yep, trying to use "Ruby red" everywhere is a bad idea. Worse even than our
Blue on blue ;-)
Java (http://java.com/en/index.jsp). Ugly. Overdone and
information-free.
Interesting, I never go there. The real Java home page has always been:
http://java.sun.com/
which is a completely different experience. I wonder if Sun thinks the only
people that will go to java.com are people hearing about Java for the first
time and expect a "brochure"?

You might also want to look at:

http://www.php.net/

http://www.mysql.com/

http://www.postgresql.org/

http://www.blender3d.org/ (the sell)
http://www.blender.org/

http://www.microsoft.com/net/
http://www.microsoft.com/net/technical/
http://msdn.microsoft.com/netframework/
http://msdn.microsoft.com/

http://www.macromedia.com/software/flash/
http://www.macromedia.com/devnet/mx/flash/
http://www.macromedia.com/devnet/

http://developer.apple.com/

Notice that like Sun has done with Java, there is a clear difference between
what is presented for potential customers and existing customers with .NET,
Flash MX, and Blender. Once you've bought into .NET you go to MSDN, with
Flash you go to the dev center. Once you're a customer you have a different
bookmark that you're going to keep and/or it is basically one click to get
from the home page or in the case of .NET it actually requires two or three
because they just need to "sell" a lot more and the real MS developer
already knows to just go right to MSDN.

Personally, I think the home page should have a lot more "sell" with
convenient links to the "meat" for existing developers including search on
the home page. There can be a lot of sub-pages with more of the success
stories, white papers, case-studies, audio, video, etc. but www.python.org
is the URL you're always going to give to someone that doesn't already use
Python, so we have no choice to make a good impression on the home page.

I guess I'm in favor in the long-term of treating presentation of the Python
product more like Java, Flash MX, and .NET. However, a mysql.com or php.net
site is better in the short-term. php.net probably strikes the best balance
for a single site that has good sell qualities on the home page while still
having an extremely clean design and lots of one-click links and search to
the useful stuff for existing users.

Note that the whole issue of users being able to contribute comments to
pages is a separate discussion but certainly one of the more unique aspects
of php.net. Something for us to consider in the long-run, but probably not
now.

ka
Oktay Safak
2003-08-09 18:36:36 UTC
Permalink
----- Original Message -----
Post by Kevin Altis
From: Roy Smith
As a totally unscientific survey, I just looked at a few
language-specific web sites and evaluated them according to my own
TCL (http://www.tcl.tk/). I like it. Looks professional without being
too glitzy.
This is way too busy for me.
<snip lots of links>
It's amusing that www.perl.org isn't in your list of links :-)

I wasn't particularly impressed by the "look-and-feel" of php or perl sites,
but I like the way both pages have a "What's ***" section in a very
prominent place on the first page. Their answers to this question suck from
their own marketing POV but that's their problem :-)

www.python.org also has this question but it's way down in the first page
and the answer is behind the link. I think we too should feature this
question in a very prominent part of the first page, with the answer
immediately visible. And it has to be a much better one that has good
selling/capturing qualities.

After Aahz's advice to subscribe to pyotorg-redesign, I skimmed through the
archives to see what has been said before. One thing people seem to have
agreed is that the new design should address the newcomers rather than the
veterans. That prompted me too look at the existing design from that POV.
Here is what I observed:

The current www.python.org page has no hints for a newcomer in a visible
place that Python is actually a programming language, except a vague one on
the last line of the Google quote. A newcomer needs to scroll down below the
"Announcements" section to get his first hint that Python is a programming
language. Observing this, I think this makes it evident that the current
design is actually aimed towards people already using Python --
"Announcements" surely are for people who already know and use it. The only
element on the first page that is immediately visible and has a "selling to
newcomers" idea behind it is the Google quote but sadly, it is left alone
there. Its message is correct and powerful but it needs backup from other
page elements. It would be very nice if the "What's Python" section I
described above and this Google quote were a single unit, standing out from
other elements on the page by means of a different background or some other
stylistic difference (like the Announcements section's background).

Now I'm heading to pydotorg-redesign to read more posts and to subscribe.

Regards,

Oktay
Oktay Safak
2003-08-10 22:25:42 UTC
Permalink
I continued my tour on the current site and made some observations.

I'll try to itemize these observations and ideas that followed them in a
minimum number of words. Feel free to bug me:

- Serif fonts (like Arial, Verdana etc.) are easier to read on screen and
look more modern and elegant. A switch to serif fonts would be nice.

- The "python" image at the center is *too* big, ugly and also unnecessary
IMHO

- Alignment of the Google quote is also ugly, should be centered or
justified

- Text in the content area is flushed to the right border. (I always seem to
reach the horizontal scrollbar) A small amount of right-indent would be
useful.

- It would be nice to have tool-tips on the top and left links. Not needed
by every link but some do (i.e. SIGs) Also, it might be a good way to add
some professional/designed look in a bandwidth-savvy way.

- http://www.python.org/topics/learn/ page's "Looking for a particular
Python module or application?" section recommends PyPI as the first choice
but it's not very crowded there yet (188 packages), so a message on the PyPI
page like "the index is still new, there are many many packages not listed
here yet etc." would be good from a marketing POV. A newcomer going there
and saying "only 188 packages?" is *bad* marketing.

- PyPI "tree of packages" page is looks very crowded and ugly. Needs better
style.

- There are many multiple entries in that 188. (i.e. ZODB has 8) Can the
different versions be shown on a new page after a click on the ZODB link?

- The Wiki and the FAQ links should be in either the "Special Topics" on the
left nav-bar or among the top-links.

- http://www.python.org/topics/learn/overview.html has to be improved. And
yes, the invert dictionary example is not very good (trying not to be
impolite here)

- I like the way *private* mailing-lists are hidden in SIGs page and the
public ones are exposed under Community->Mailing Lists and NGs

- I like that the left nav-bar is dynamic while the top nav-bar is static

- Announcements section should be moved into a box on the right, perhaps
with just the most recent one highlighted right below the top nav-bar.

- bread-crumbs would be very nice (I've seen the prototypes by Tim and
Walter)

- The main text area should feature the question "What's Python?" and our
answer and the Google quote. (I know I said this before)

OK, that's enough brainstorming for now.

Regards,

Oktay
Aahz
2003-08-11 00:00:20 UTC
Permalink
Post by Oktay Safak
- Serif fonts (like Arial, Verdana etc.) are easier to read on screen and
look more modern and elegant. A switch to serif fonts would be nice.
I'm opposed to using the web as a substitute for PDF. All browsers have
the ability to specify fonts of the user's choice; it's not our place to
muck with that. Similarly, I *always* use <font size="+1"> to do
relative font size changes instead of absolute.
Post by Oktay Safak
- The main text area should feature the question "What's Python?" and our
answer and the Google quote. (I know I said this before)
Haven't had a chance to mention this yet, but I think the set of links in
the top navbar should be:

* Home
* Why Python?
* Getting Started
* Documentation
* Community
* Sitemap
* Developers

The reason I say "Why" instead of "What" is that I think most people
going to www.python.org already have a vague idea what Python is, and we
can still make "What is Python?" fairly prominent, just not part of the
navbar.
--
Aahz (***@pythoncraft.com) <*> http://www.pythoncraft.com/

This is Python. We don't care much about theory, except where it intersects
with useful practice. --Aahz
Dylan Reinhardt
2003-08-11 02:40:08 UTC
Permalink
Post by Aahz
Post by Oktay Safak
- Serif fonts (like Arial, Verdana etc.) are easier to read on screen and
look more modern and elegant. A switch to serif fonts would be nice.
I'm opposed to using the web as a substitute for PDF. All browsers have
the ability to specify fonts of the user's choice; it's not our place to
muck with that.
Using CSS to specify a font (and gracefully degrading to a font family)
isn't much of an imposition... really, it's just a recommendation.
Users who choose to specify their own fonts can easily override CSS
recommendations, particularly if we stick to common tags like <P>.

Font specification seems justified if it provides an enhanced experience
for most visitors and an undiminished experience for all others.

$.02,

Dylan
Oktay Safak
2003-08-11 08:34:59 UTC
Permalink
Post by Aahz
Post by Oktay Safak
- Serif fonts (like Arial, Verdana etc.) are easier to read on screen and
look more modern and elegant. A switch to serif fonts would be nice.
I'm opposed to using the web as a substitute for PDF.
I'm not proposing that. Just a change of the font-family, no big deal.
Post by Aahz
All browsers have
the ability to specify fonts of the user's choice;
In theory. I don't know where that choice is on IE. And if it's there I bet
99% of the population wouldn't know either.
Post by Aahz
it's not our place to
muck with that.
I don't understand what's bad with providing with a better default font.
Post by Aahz
Post by Oktay Safak
- The main text area should feature the question "What's Python?" and our
answer and the Google quote. (I know I said this before)
Haven't had a chance to mention this yet, but I think the set of links in
* Home
* Why Python?
* Getting Started
* Documentation
* Community
* Sitemap
* Developers
The reason I say "Why" instead of "What" is that I think most people
going to www.python.org already have a vague idea what Python is,
Yep.
Post by Aahz
and we can still make "What is Python?" fairly prominent,
This is what I'm suggesting.
Post by Aahz
just not part of the navbar.
I didn't say anything like that.

Regards,

Oktay
Richard Jones
2003-08-11 07:55:52 UTC
Permalink
Post by Oktay Safak
- http://www.python.org/topics/learn/ page's "Looking for a particular
Python module or application?" section recommends PyPI as the first choice
but it's not very crowded there yet (188 packages), so a message on the
PyPI page like "the index is still new, there are many many packages not
listed here yet etc." would be good from a marketing POV. A newcomer going
there and saying "only 188 packages?" is *bad* marketing.
Wow, there's 188 packages already! Python 2.3 (the first python with built-in
PyPI support :) was only just released...
Post by Oktay Safak
- PyPI "tree of packages" page is looks very crowded and ugly. Needs better
style.
Quite open to suggestions here... The code is at http://pypi.sf.net/ if you
wish to play with it (I can provide the current package database for
testing).
Post by Oktay Safak
- There are many multiple entries in that 188. (i.e. ZODB has 8) Can the
different versions be shown on a new page after a click on the ZODB link?
The problem here is that package authors are free to apply any bizzare version
numbering scheme they wish to their packages, so figuring out the most recent
entry can be .. fun :)

Also, some package authors (myself included) wish to have several versions
appear in the index at once - a stable version and a development version (or
three as the case may be).

To this end, I opted to use the sourceforge approach of retaining all
versions, but allowing the package maintainer to hide older versions. Those
don't appear in any browsing or searching, but it requires that the package
maintainer hide them. So far, I'm getting a mixed level of buy-in on this.
I've been considering sending out emails to people who have more than four or
five visible versions...


Richard
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: signature
Url : http://mail.python.org/pipermail/pydotorg-redesign/attachments/20030811/f3f64e9f/attachment.bin
Steve Holden
2003-08-10 22:53:15 UTC
Permalink
-----Original Message-----
Sent: Sunday, August 10, 2003 5:24 PM
To: Pydotorg-Redesign
Subject: [Pydotorg-redesign] Some quick observations and ideas about
thecurrent site
[...]
- Serif fonts (like Arial, Verdana etc.) are easier to read
on screen and
look more modern and elegant. A switch to serif fonts would be nice.
[...]
The fonts you mentions are *sans-serif* fonts (i.e. fonts without
decoration on the letter stems). I agree that Verdana is a good
general-purpose web font. Arial less so, but an acceptable substitute
when Verdana isn't available.

regards
--
Steve Holden http://www.holdenweb.com/
Python Web Programming http://pydish.holdenweb.com/pwp/
Oktay Safak
2003-08-11 08:03:37 UTC
Permalink
Oops, you are right. Sorry, late night posting.

And I agree with you about Verdana and Arial.

Regards,

Oktay


----- Original Message -----
From: "Steve Holden" <***@holdenweb.com>
To: "Oktay Safak" <***@ixir.com>; "Pydotorg-Redesign"
<pydotorg-***@python.org>
Sent: Sunday, August 10, 2003 2:50 PM
Subject: RE: [Pydotorg-redesign] Some quick observations and ideas about
thecurrent site
Post by Steve Holden
-----Original Message-----
Sent: Sunday, August 10, 2003 5:24 PM
To: Pydotorg-Redesign
Subject: [Pydotorg-redesign] Some quick observations and ideas about
thecurrent site
[...]
- Serif fonts (like Arial, Verdana etc.) are easier to read
on screen and
look more modern and elegant. A switch to serif fonts would be nice.
[...]
The fonts you mentions are *sans-serif* fonts (i.e. fonts without
decoration on the letter stems). I agree that Verdana is a good
general-purpose web font. Arial less so, but an acceptable substitute
when Verdana isn't available.
regards
--
Steve Holden http://www.holdenweb.com/
Python Web Programming http://pydish.holdenweb.com/pwp/
A.M. Kuchling
2003-08-11 12:02:02 UTC
Permalink
Post by Aahz
Haven't had a chance to mention this yet, but I think the set of links
in
* Home
* Why Python?
* Getting Started
* Documentation
* Community
* Sitemap
* Developers
Assuming "Getting Started" goes to /topics/learn/, the only one of
those links we don't already have is "Why Python?". Would that point
to the existing /doc/Intros.html, or do we need to make a new
advocacy/marketing section? If the latter, we need someone to step up
and volunteer to actually write it. (That person won't be me; my plan
is to revise the FAQs and then go off and work on a Quixote web site.)

--amk
Aahz
2003-08-11 15:35:44 UTC
Permalink
Post by A.M. Kuchling
Post by Aahz
Haven't had a chance to mention this yet, but I think the set of links
* Home
* Why Python?
* Getting Started
* Documentation
* Community
* Sitemap
* Developers
Assuming "Getting Started" goes to /topics/learn/, the only one of
those links we don't already have is "Why Python?". Would that point
to the existing /doc/Intros.html, or do we need to make a new
advocacy/marketing section? If the latter, we need someone to step up
and volunteer to actually write it. (That person won't be me; my plan
is to revise the FAQs and then go off and work on a Quixote web site.)
It'd be a new advocacy section; I think we have most of the material to
assemble one. I certainly don't expect you to do it -- you've been doing
a wonderful job recently, but it was a *lot* of intense work. I just
wanted to get agreement that this was a good direction. We could point
at Intros.html if we wanted to change the navbar now, but that's not a
long-term solution

Do you agree that "Getting Started" is a good name for the link?
--
Aahz (***@pythoncraft.com) <*> http://www.pythoncraft.com/

This is Python. We don't care much about theory, except where it intersects
with useful practice. --Aahz
Jack Jansen
2003-08-11 15:15:24 UTC
Permalink
Post by A.M. Kuchling
Post by Aahz
Haven't had a chance to mention this yet, but I think the set of
links in
* Home
* Why Python?
* Getting Started
* Documentation
* Community
* Sitemap
* Developers
Assuming "Getting Started" goes to /topics/learn/,
Well, there's more to getting started, such as finding out whether you
have Python
installed already (RH, OSX), and how to install it if you haven't.
Post by A.M. Kuchling
--
Jack Jansen, <***@cwi.nl>, http://www.cwi.nl/~jack
If I can't dance I don't want to be part of your revolution -- Emma
Goldman
Loading...