I think the documentation section needs to be organized. I count over two dozen links in a simple list with no apparent organization. Some (like "copyright") might be best under some other heading, like downloading. Some are minor topics, or of transient interest, such as moving from 3.4 to 3.5. Some, like v2 docs, are obsolete but still needed somewhere. The "5 minutes or less" probably deserves to be a big button on the front page --- that's the programmer's equivalent of eye candy. Overall, I find that the most important docs (the v3 API and API reference) are buried.
I suppose the best way to approach organizing this is to look at what other free software sites do. Just to pick the first on your list, http://www.postgresql.org/docs/ looks like a reasonable way to go. Each version has its own heading. Manuals are separated from What's New, FAQs, etc., user documentation (API) separated from internals, etc. Maybe that's a good template for organization. Liam Liam ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
