[SciPy-dev] Scipy.org

Andrew Straw strawman at astraw.com
Sat Dec 17 12:41:15 CST 2005

Joe -- fantastic ideas. I've taken this opportunity to convert
http://astraw.com/scipy (aka http://scipy.astraw.com ) from a
kick-Moin's-tires into the "staging area" suggested. (If I could set up
new.scipy.org, I would...) I've also used Mark K's ideas about using
sinorca4moin as the default theme.

I haven't set up the site structure "for real" yet (with, for example,
what Joe suggests) because this decision will be with us for a long time
and I want to make sure we get some consensus on this. (There is
currently some site structure in the staging area -- I copied it blindly
from the current scipy.org when I set up that site and should be
ignored.) When we decide on the "top-level" pages, I will edit the moin
configuration file to have those placed in the navigation strip.

Now, for my personal opinions about Joe's overall layout: I would prefer
taking a "portal to the universe of Python software for scientific
computing" approach, with scipy_core and full scipy being locally hosted
and emphasized players in that universe. As such, I'd prefer an
organization more like the following.

        sidebar with brief news summary
        (e.g. scipy_core and full scipy nearing end of heaving
Getting started
        simple demos using scipy_core and matplotlib, for example
        pointers to individual packages, both scipy and external
        made with matplotlib and scipy_core and/or full scipy
        made with MayaVi
        made with raw VTK
        benchmarks from 64 CPU 64 bit Itanium system
        Intro demos
        Download page with links to source and binary releases
        Info about svn, link to Trac
(full) scipy
        Intro demos
        Download page with links to source and binary releases
        Info about svn, link to Trac
        we should
        think about
        some organization
        for code receipes
        point to (or include) scipy_core/Download and scipy/Download

Joe Harrington wrote:

>While I agree with Travis on the state of the web site content (so
>much out of date that it all bears going over before posting on the
>new site), the random approach is how we got the mess we have now in
>the first place.  It wasn't Plone that did it, it was us (or the lack
>of us).
>We are about (I hope, I dream, if I were religious I'd pray) to
>blossom into a popular site, with the majority of visitors not being
>developers and maybe not being more than budding scientists.  The
>organization that developers or experienced users want will not meet
>the needs of a high-schooler who is using scipy to do a homework
>assignment for the first time on her school computer.  Organic design
>works when everyone's goals are in line.  Site visitors' goals are
>divergent, so letting the site "grow" in a pure-wiki way will make
>finding your way around the site like navigating a rose bush: beauty
>all around, but too painful to get to.  We have some web design
>experts among us.  Let's design a site structure that has room to
>grow, and slot content into it, rather than letting the site design
>evolve organically.
>It makes sense (to me) to have some "start here if you're a ..."
>pages that present an introduction to the appropriate audience and
>then index into the main site content.  How to present these without
>slowing down the experienced user or developer is the question.  It's
>not hard to think up successful strategies, but they may depend on a
>particular underlying organization, so we should do a little thinking
>before we start.
>I suggest a two-pronged approach:
>1. Set up a staging area for the content itself.  It should have a
>   flat organization: items go in its top level for discussion and
>   review before being moved into the main site.  Items shouldn't stay
>   here long.  Doing this lets conversion start before we have a site
>   structure.
>2. While (eager!) content authors are moving their stuff over to the
>   Moin staging area and updating for the new scipy, we all have a
>   discussion of site organization, including input from web experts.
>   Then, set up the structure and move over the content.
>Meanwhile, keep the current plone site up, with a note at the top
>saying what's going on (new Scipy, numeric and numarray unified, new
>site in development, discussion on how to organize it HERE, content
>conversion HERE, nothing new on this site, thanks for your
>indulgence).  Set up the Moin site as new.scipy.org, and hang the
>staging area off it as new.scipy.org/staging.  Be open about our
>process but don't stick it in newbies' faces until there's something
>there to stick.  There will be a switchover time, likely before the
>new site is polished up, but it's not now.
>To begin with, I've made two lists.  The first is a list of potential
>site user types.  The second lists categories of content.
>Website Accessors
>New, inexperienced user
>New user experienced with similar software (IDL, Matlab)
>Existing user looking for
>	news
>	updates/downloads
>		software
>			main
>			add-on
>		docs
>	place to report problem/track problem reports
>	talk with other users
>		seek advice
>		give suggestion
>		help others
>		search for past coverage of issue
>	resources on a topic
>		links elsewhere
>		topical page
>	all of the above
>	talk with other developers
>	active sources (SVN)
>	web posting
>Potential user
>Potential customer/employer
>Website Areas
>"What is"
>	summary page
>	demos on web
>	demos you can run
>	links
>Getting Started
>	install
>	intro docs
>	intro demos
>	community links
>	packages
>	docs
>	mailing lists
>	events
>	presentations
>	user area
>	past events
>	bug reports
>Media kit
>Advocacy kits
>Scipy-dev mailing list
>Scipy-dev at scipy.net

More information about the Scipy-dev mailing list