Website needs to be suitable for 2.0

[hypatia]

This is related to 697, but this bug lists the features the website really ought
to have at the time of the 2.0 release. Hence the priority rating.

So:
 - individual websites for projects
 - good basic navigation that directs people to each project
 - ability for project maintainers to alter websites using some kind of
template? (or will this be part of the automated release process?)

Please add further comments below.

[hypatia]

<itamar> the whole /services/ /about/ etc. has to be redone
<itamar> to change the focus to the fact we have multiple projects
<hypatia> right, so it's really content, not, say, web programming or anything
<itamar> so like, front page should make it obvious which project you want
<itamar> mostly, yeah

[glyph]

It's worth nothing that this website upgrade should NOT break existing URLs. 
There are a lot of other websites pointing at various places, especially
"/products/twisted".

[hypatia]

I'm not planning for it to do that, but I'm not really clear on what /products
is meant to be, and how it should relate to /projects (which is where the
project websites have all been put, and which will presumably need an index file
which will look pretty much like /products )?

So, is there a difference between a Twisted Labs "product" and a Twisted Labs
"project"? If not, how do the two URL hierachies work?

[glyph]

The existing hierarchy can just be reformulated as redirects to the new
hierarchy - it isn't necessary to update the old pages, or to maintain the old
hierarchy's meaning, just to make sure that they still point to something useful.

[hypatia]

Any good ways to do 301 or 302 redirects? I think that would need to be done
inside the code that runs this vhost :(

[itamarst]

.rpys, probably.

[hypatia]

Thanks, .rpys have never really bene on my radar but I know how they're meant to
work.

[hypatia]

Some more notes towards this:

/documents will disappear and be replaced with /projects/BLAH/documents or
similar, radix can you do the script for this?

Front page may still link to some of the over-view documents, say FAQ(s) and
tutorial.

[hypatia]

Assuming that the project website code I did for radix is sufficient I think
this is "close enough" save for one thing: the redirects. Notes are in
index.html in my branch :)

The /products directory is not yet entirely empty, but I don't think that should
be considered sufficient to hold up the release by itself!

[radix]

Getting close. I merged the new projects directory and it's now live on the 
site. Still need to update the front page and do redirects. Before I do the 
frontpage I need to figure out what to do to make the old releases still 
navigable...

[hypatia]

I've added a twisted pair website data file. radix needs to do a couple of
things for that:

 1. Update it with the maintainer's name and email
 2. Update it with the md5 sum (me downloading it from MIT and computing it here
is rather beside the point)
 3. Regenerate the website

Then I'll create a new non-urgent bug about updating the pair website for the
maintainer.

[hypatia]

One more thing: someone pointed ot that the project sites don't link to the API
docs.

[radix]

did the pair stuff. the API docs aren't linked to because the API docs 
don't exist, and that isn't a 2.0-urgent issue, afaic.

[hypatia]

OK. If there's nothing else 2.0-urgent this bug should be closed and others
opened for remaining issues. Anything spring to mind?

[radix]

nope, I agree. resolving.