BCF Website design principles, structure and procedures

1. Design Principles

A. The website must be groovy, sharp, appealing, interesting, easy-to-use, informative and regularly updated.

B. Must be easy for people to maintain in various functional areas.

2. Structure

A. The website is designed around functions and sub-functions.

B. There is an overall webpage with general details and general links, but most material is found in functional areas underneath that, i.e. specific culture or activity groupings like the art, music or community and spirituality pages.

C. Each functional area has a separate sub-directory with separate upload username and password permissions, to prevent errors and cross-contamination. Check with John for details.

D. All graphics for a particular function or sub-function are kept in the same directory.

E. The website structure is stored in a file webstructure.html in this current directory.

3. Procedures

A. Uploading or updating pages and information: Log in to the server with the correct username and password. Use ftp to upload or overwrite files. Store all related text and graphics in the same directory. If the directory becomes unmanageable, consider creating a separate sub-function area and store all related text and graphics for that function there.

B. Link to other relevant pages within the overall site where possible, by pointing to the highest level- i.e. the functional level. This page will be called index.html in that directory.

C. The main page in each functional area (and therefore separate directory) will be called index.html.

D. You can use any page making software, but preferably use one that is easy to maintain and uses minimal extra stuff in it (e.g. please don't use micros*ft frontpage because it's a mess!)

E. Check with the webguru if in doubt.