IT Services | Services | Web Services | Web site creation and redevelopment

Document Actions

Web site creation and redevelopment

The usual procedure that we (the ITS Web Team) would expect to follow in the case of a web site creation or redevelopment project for a School or Department (the client) is as set out below. All sites are created using Birkbeck's Plone content management system unless otherwise agreed with the client.

  1. The client contacts the Web Content Manager in External Relations (j.vandeban@bbk.ac.uk, 020 7380 3132) to discuss the planned project.

  2. The ER Web Content Manager liaises with the Web Team concerning the requirement.  One or more meetings may be arranged between the client, the ER Web Content Manager and the Web Team to allow a full discussion of options and project phases, if necessary.  

  3. Once the project has been agreed and scheduled, the Web Developer assigned to the project and the client agree the project specifications and timetable in detail for the whole project or, if a phased project, for the first phase.  The project specification will include areas of responsibility, with the client usually undertaking all content work and providing the necessary images and colour scheme choices while the Web Developer undertakes all the technical development work.  Training for for content creation and maintenance is provided through scheduled training events and/or one-to-one sessions as required.  Editorial help may be available from the ER Web Content Manager if the project timings, existing commitments and College priorities allow. The project specifications must be signed-off by the appropriate senior member(s) of staff within the School or Department before development work commences.

    Project specification changes
    Changes to the project specification after the initial agreement will usually lead to the project having to be re-timetabled as a new project, leading to considerable delays.  It is therefore vital that the project specification is clearly defined and understood by the Web Developer and the client at this stage.

    Design
    The most recent iteration of the standard School/Department design template will be used, with colours and images chosen by the client to customise the site.  Resources are too limited to allow for the creation of bespoke design templates.

  4. The Web Developer creates the site on the test server to the agreed specifications and following the agreed timetable.

  5. The Web Developer, ER Web Content Manager and client liaise on a regular basis appropriate to the scale and length of the overall project, via email or through face-to-face meetings.  Issues that might impact on the agreed specifications or timetable must be raised as soon as they arise, so that changes can be discussed and agreed by all concerned.

  6. The client inputs the site contents as agreed, possibly with the help and support of the ER Web Content Manager, tests the site and reports problems/issues to the Web Developer.

  7. The Web Developer discusses with the client any problems/issues raised and both agree the appropriate action required to address these.

  8. The Web Developer carries out the agreed actions.

  9. The client carries out final tests and then signs off the project.

  10. The Web Developer and Web Systems Administrator set the site live according to a timetable agreed with the client.

  11. The client and Web Developer monitor the use of the site during the first live month and discuss and agree any necessary snagging work.

  12. The client and Web Developer carry out the agreed snagging work.

  13. The client continues to maintain the content of the site and cascades training to new content maintainers within the School/Department on an ongoing basis as required.