Suggested Structure

To meet the needs of the project the site will, in essence the site will be split into two public faces, both faces however will share the core database and branding:

Repository

The primary user will be the (prospective) AT user. This part of the site will allow users to find appropriate OS software for their needs. The repository will:

• Allow a range of search and browse mechanisms to find software – appropriate for a range of levels.
• Present the process in clear steps
• Hide the user from any ‘raw’ program stores
• Allow potential download of software within 3clicks from front page

Software available will:

• Follow standard download and install steps
• Pre-packaged to standard spec to ensure ease of install

Forge

The primary user will be the (prospective) AT developer. This part of the site will provide a code store and development resources for new OS AT software.

• Code store
• Executable store
• Bug Tracking
• CVS
• Forums

Issues

Database

What should go into the database? Do we need a database, or can we start with linked documents. Easier to build the database once we have a good idea what the content will be.

simon: See the attached file for the suggested DB content and the mind map for the structure (files duplicated on PLONE). I am currently adding trial structure to the site.