CSU Web Design Process
Step-by-Step Web Design Process
- Getting Started
- Graphic and Layout Design
- Validation and Accessibility
- Proofing and Link-Ups
- Go-Live and Handover
Log an IT Service Desk request on the Division of IT website.
An initial meeting will be arranged to discuss the scope of the website and navigation structure.
- Deadlines will then be outlined and the best case “Go Live” dates fixed.
- You will be asked to provide information such as, finalised menu items, preferred images and title for the construction of the graphical shell to house the new website. Pre-approved styles are already set for various areas within the University. For example Divisions have a certain style as do Enterprises, Schools and Faculties. Flexibility with colours and graphics are provided for customisation. See CSU Web Style Guide for more information.
- A “Page Curator” will need to be nominated for the ongoing maintenance of the website. A definition of the Page Curators role can be found in the CSU Web Policy. This “Page Curator” needs to arrange to complete the Page Curator Induction and either Dreamweaver or Content Management System Training, either both determined and provided by the IT Training group. A Page Curator needs to have completed this training before access will be granted to maintain the website.
The location of your website is discussed and decided on. Most addresses will be created dependent on the sites relation to the particular area. For example the area the client is from in the University.
Marketing promotional sites with a limited life span are usually located under the /student/ directory. Special needs addresses, such as top level directories are restricted and can only be approved through submitting a request to the Website Management Committee. Only sites with the Committees approval will be granted these addresses. For example – http://www.csu.edu.au/mynewsite/
- The CSU web designers prepare a graphical shell (according to the web style guide) and this is sent to you via email for proofing. This shell is located on a development area, only viewable by CSU Staff for review. You can identify that a page is on the development server by the web address that is in the browsers address bar. All development server addresses will either have a prefix of “wwwdevel.csu.edu.au” or “cms.csu.edu.au” (depending on their location) in the website address as apposed to “www.csu.edu.au” for a live public website.
- Usability issues are addressed. Comments, feedback and changes are noted and implemented.
Finalised content needs to be resolved before work commences on the website. It should be:
- Written in a manner specifically for CSU web delivery (Please contact Marketing for help editing and writing your content.)
- Provided electronically in Microsoft Word documents. Additional instructions if needed should also to be provided in this manner. Please try to keep content to simple text. Formatting will be applied when it is placed into the web site.
- Copyright of all material should be checked and approved if needed. More Information see – http://www.csu.edu.au/copyright/
- Reviewed, approved and finalised for inclusion in initial construction of site. Minimal changes will be made after initial delivery. Other minor content changes will need to be done on site hand over by your specified page curators. Major changes will need to be assessed by your web developer and may require additional jobs to be logged.
- Associated attachments and other files also need to be provided. (PDF files, forms, images etc.) When providing .pdf files a .doc file also needs to be provided as an alternative so the document will be accessible to all users. If you wish to include video meant for external audiences (e.g. prospective students, alumni, researchers, business etc) or in university communications to commencing/continuing students and staff, please first refer to the Charles Sturt University Video Guidelines [.pdf].
- A location on the S: drive in the common folder can be created for storage of this information. Please ensure this location is not the primary source of your content. It must be a copy taken from another location. S drive common folders will be emptied according to the duration of the folder chosen. For example - S:\Common\ Temp Folder Less Than 60 Days\my web site
The site is checked against CSU Web Accessibility policy and tested for browser compatibility. To ensure the delivery of a high quality web site the following tests are conducted –
- All new web pages are validated using the W3C Validator.
- Page quality to address accessibility, meta tags, page download, broken links etc.
- Web browser compatibility using a minimum 800 x 600 screen resolution.
- Usability and peer testing
- Existing Link checks for structure and ways of navigating to the site. Additions of links to staff.csu need to be logged with the IT Service Desk.
The site is tested for accessibility issues. For example the site may be tested in a text to speech browser or via key board only access. Any inconsistencies are rectified. This ensures that the site can be accessed by those with special needs.
The web site address on the development server (wwwdevel.csu.edu.au or cms.csu.edu.au) is emailed to the you for final proofing. Any small final changes are made.
Discussions are had about other locations on the CSU website which would be appropriate to have a link to the client’s new website. These are noted and implemented on the “Go Live” date.
If the scope of the website has changed and further development is required after you have given final approval to go live an additional request will have to be placed with the IT Service Desk. Once you approve the website it is put live on the CSU public web server and any additional links implemented.
Any major changes will need to come back to the Web Design and Development area for approval. An assessment can then be made of the work required and allocated to the Page Curator if appropriate.
Site Life & Review
Development of graphical changes, online forms and other routine maintenance can be completed by The Web Design and Development Team if required and can be instigated by logging a call with the IT Service Desk.