We’re working with schools to test out content and prepare for our new website editor.<\/p>\n
Earlier this year we launched a set of initial top-level pages<\/a> based on our new website theme.<\/p>\n The next step has been exploring content from our academic schools.<\/p>\n Following on from the initial prototypes, we are now continuing with refining these concepts in preparation for Site Editor (the Dreamweaver replacement publishing system).<\/p>\n The purpose of the school pilot project is to:<\/p>\n We want to learn how our new design works in providing the content our customers<\/a> need from schools, similar to the beta website<\/a><\/strong>, we launched for the top-level pages.<\/p>\n It is a chance to experiment with content ideas<\/strong> alongside our business stakeholders and help us to get ready for the next step: Site Editor<\/strong>.<\/p>\n We want to provide a framework that allows web editors to focus more on user-centred content creation<\/strong> and less on design\/layout\/development technicalities.<\/p>\n The intention is to benefit our customers who receive a unified user experience<\/a> which extends to a better perception of the university<\/a>.<\/p>\n As part of the project, we’ll be defining a range of page types that make it easier for web editors to create content.<\/p>\n The designs and patterns will be developed by the IS Web Teams.<\/p>\n We will be eventually moving to Site Editor which will use a templated approach. These templates will be created based on the school pilots and therefore the school pilots need to work within those designed templates.<\/p>\n The idea of a ‘template’ shouldn’t be scary, they will not be as restrictive as they sound! They will allow a broad range of exciting content configurations<\/strong> to present what is needed for the content.<\/p>\n Consistent patterns and templates provide many benefits:<\/strong><\/p>\n Based on analytics, we are defining a key set of pages to form the default navigation structure for schools:<\/p>\n A lighter structure benefits both web editors and users making the site more manageable and maintainable. This will be extendable where required.<\/p>\n As we remove the technical barriers of\u00a0Dreamweaver, we’ll move towards a content-focussed approach.<\/p>\n To help support web editors, we’re developing a content guide which will be based on the outputs of the project.<\/p>\n This will provide a foundation in creating effective online content.<\/p>\n Imagery is a key aspect of the new design. Not every page requires bold imagery (although good imagery should be used in all cases).<\/p>\n For the limited ‘showcase’ pages, good, quality imagery is vital in achieving the design aesthetic<\/a>. We are working on image guidelines<\/a>.<\/p>\n We’re also planning to provide inline help in Site Editor based on our recent user testing<\/a>.<\/p>\n Site Editor is a system to make it easy to create online content using our new web theme.<\/p>\n Once we’ve finished the school pilots, we’ll be able to define the various templates and patterns that Site Editor will use to create content.<\/p>\n In the meantime, you can prepare your content by:<\/p>\n We’re taking stock of where the pilot school sites are at the moment and will progress with Sport and Exercise Science as our first pilot to complete. We’re aiming for 18th September.<\/p>\n Following this we’ll then be working with KBS and Architecture to scope our timings, but hoping to have all pilots completed by the end of the 4th quarter.<\/p>\n We are working on Site Editor at the moment in parallel to the pilot schools as this\u00a0work is helping to inform the Site Editor requirements.<\/p>\n We’ll keep you updated on our progress on this blog.<\/p>\nPurpose<\/h2>\n
\n
Defining patterns\u00a0and templates<\/h2>\n
\n
\n
Focussing on content<\/h2>\n
Site Editor<\/h2>\n
What should I be doing now?<\/h2>\n
\n
Next steps<\/h2>\n
See also<\/h3>\n