The goals for this project included:
- integrating the site into a new template framework
- along with reviewing the IA and voice and tone, align the visual communication and interactions to ensure ITS messaging was more user-focused and friendly
- using a dashboard style for the front page
- improve consistency of messaging across ITS applications – including developing a common visual language to be used across the ITS website and the service desk applications
The tools I used in this project included:
- Fireworks (wireframes, mock-ups and functional specifications)
- Bootstrap (HTML prototype / template framework)
- Squiz Matrix CMS
- HTML, CSS, jQuery
- Photoshop (image editing)
- Basecamp (team / stakeholder comms)
Team sketching sessions
Each of our team was asked to come up with a critique of the existing page and provide some quick concepts about how they would improve the front page, to discuss as a group. This was my version. My goal with this design was to visually clarify the process, make self-service options more prominent and make all of the important information accessible up front.
Support / handover site
This was the first support / handover site that I created entirely online (previously provided in Word/PDF documents) to assist site editors and maintainers with site administration tasks.
Sharable and discoverable repository
The purpose of these sub-sites was to make the content more sharable and linkable in a modular way (eg to be able to share instructions for specific tasks) and to include the site maintenance tools (eg. news builders, content management dashboards) together in one spot.
Embedded, findable and discoverable
These were linked under a /support folder in the main site, but had permissions assigned to it so that only logged in maintainers and administrators could view it.
Certain sections could be maintained within a central repository and nested within each site, so that we could maintain an authoritative hub of information for web maintainers.
Other sections were relevant only to that sub-site and could be updated and extended by site maintainers according to their particular needs after handover.
Content Management Tools
Content management tools were built into the support site that enabled users to sort tasks by status, owner, reviewer, title, parent, etc...
Maintainers could preview a range of content meta information could be viewed at the top of any site page in the site by using a URL prefix (or a bookmarklet). Including page goals, meta descriptions, search terms, and other meta information.
I created some asset-builders to allow site maintainers to create new content easily via a form / WYSIWYG interface, such as adding new news items.