Re: Ready to launch?

> -----Original Message-----
> From: Robert Treat [mailto:xzilla(at)users(dot)sourceforge(dot)net]
> Sent: 20 December 2004 16:07
> To: Dave Page
> Cc: pgsql-www(at)postgresql(dot)org
> Subject: Re: [pgsql-www] Ready to launch?
>
>
> 1) "about the new website" link in the announcement doesn't
> go anywhere,
> did someone have content for that?

Link removed for now.

> 2) Under About->Press we have a link to the 8.0 press kit and
> in the FAQ
> it stats 8.0 is the most recent version. Perhaps those links
> should be
> hidden for now?

Done.

> 3) Downloads->BitTorrent-> only has links to the 8.0beta4,
> can we get a
> copy of 7.4.6 and 8.0rc1 ?

Added.

> 4) More of a IMO thing, but I think the links in
> Documentation->Manuals->[current|archive] should be changed
> so that with
> user comments is listed first.

Done.

> 5) Documentation->FAQ seems fairly busted. Since we have all of the
> language FAQ's working on the current site, I think this needs to be
> straightened out before we go live.

Links pointed to auto-updating docs from CVS.

> 6) Books should probably be listed in order of Publish date, an added
> bonus would be to link to the book information on techdocs (reviews,
> recommendations) but not a deal breaker.

Not done yet.

> 7) I think we should add gborg, pgfoundry, and techdocs to
> Community->Resources. possibly devrim's blog roll too, though I dont
> know if that is live yet.

Done (the first 3)

> 8) Support->professional services is blank, we either need to
> import the
> info from techdocs are create a link to it.

Links pointed to techdocs for now.

> 9) Support-> hosting is also blank, same story as #8

Links pointed to techdocs for now.

> 10) Support-> bug reporting probably should have a link to the
> pgsql-bugs archives.

Done.

> 11) Should the license link in the footer point to the license of the
> website?

Left as-is (licence applies to code and site).

> 12) Anyone else have an issue with the footer links sometimes
> overlapping the sponser add? I get this alot in the community
> section of
> the website.

Probably an issue with certain versions of Gecko (now fixed) given the
reports on the list. I haven't looked at this.

Regards, Dave