This page partly duplicates the web Download page which is out of date. For the new (drupal?) web pages we have to think about this carefully. The end users must have up to date information which is easy to read and find. Here is one possible page structure. The name of the page is "Download". It includes both downloading and installation instructions.

I don't know how valuable the "Packaging" wiki page is if the web page has up to date list of package locations.

Top level

• A short notice about the licence, like in the About dialog of the application (and link to full licence). Is there need for a "Licence" navigation link in the navigation bar?

Windows

• system requirements (there are no documented requirements atm but BT doesn't work on ANY Windows)
• known bugs (from the 2.5 release announcement which is in the wiki)
• notice about installing works, link to the Works section below
• link to latest version (must be kept up to date)
• link to top level sf.net download page?

Linux and *nix

• Data from the wiki page (the web page is out of date)

Each distro/OS

• short help and/or package location(s) for the distro

MacOS X

Works (modules)

Short help from the web page

Installing from the source code

links to development build page and packagers' page