In mid to late 2014 I worked on design and CMS development of the Student Hub with Melbourne Students and Learning at the University of Melbourne. The goal of this initial project phase was to establish a foundation towards bringing key information together from a diverse range of sources into a unified interface, with the goal of making this important information easy to find and to create a more seamless, cohesive and reliable experience for students.
Working alongside project managers, marketing experts, UX researchers, testers and content developers, my role focused on:
- reviewing research, requirements and briefing documentation
- developing wireframes / mock-ups & HTML prototypes
- design advocacy in client/team meetings, presenting designs, consolidating feedback and adapting product
- web design and CMS template development
- developing support documentation including style guides for site maintainers and delivering training to a small group of editors
The tools I used in this project included:
- Illustrator / Acrobat (wireframes and functional specifications)
- Bootstrap (HTML prototype / template framework)
- Squiz Matrix CMS
- HTML, CSS, jQuery
- Photoshop (image editing)
- Wave, colour contrast checkers and W3C code validators
- Basecamp (team / stakeholder comms)
- Git (site back-ups, basic versioning)
Handover & support documentation
A site that is maintained and nurtured is one that is going to be most useful and reliable for it's users!
Along with custom handover training to individuals and small groups, a support site was provided to site administrators and maintainers. This was located inside their site folder for easy access.
The support site provided custom site-building tools and instructions specific to maintaining their site, as well as links into relevant information provided elsewhere by internal and external web communities to help them with their maintenance tasks.
Easy to implement, build and extend
Each support site I built was based on a standard 'base template' so it could be implemented quickly for each new project. It used nested content areas for efficient reproduction, ease of updates and consistency of messaging, but was also easily customisable for each client or project. Site administrators could easily build upon it and extend it to meet their needs.