1 / 45

One CMS to rule them all? Sue Steele Manager ITS Web Centre

One CMS to rule them all? Sue Steele Manager ITS Web Centre. Utilising a Content Management System. Choosing an appropriate model for your business Exploring ways to simplify content migration Realising how your CMS can impact on user experience Getting your CMS to be fully accessible

raimondo-brooke
Download Presentation

One CMS to rule them all? Sue Steele Manager ITS Web Centre

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. One CMS to rule them all? Sue Steele Manager ITS Web Centre

  2. Utilising a Content Management System • Choosing an appropriate model for your business • Exploring ways to simplify content migration • Realising how your CMS can impact on user experience • Getting your CMS to be fully accessible • Brief case study

  3. Utilising a Content Management System • Choosing an appropriate model for your business • Exploring ways to simplify content migration • Realising how your CMS can impact on user experience • Getting your CMS to be fully accessible • Brief case study

  4. Let’s pick a CMS • A CMS should produce web sites that align with organisational goals • This should be easy • Develop your web site’s goals • Based on site goals, decide the functionality you require from a CMS • Evaluate available CMS and choose the best fit

  5. Lets pick a CMS • CMS come in all shapes and sizes • Some are open source, some cost a great deal of $$$ • Some publish stand-alone sites, some are tightly integrated with the published web site • Some we don’t even think of as CMS at first

  6. But … • Not all web sites have the same goals and needs • Intranets may have very different goals compared to public sites • The CMS that delivers on one may struggle to deliver on the other if the goals are vastly different

  7. Utilising a Content Management System • Choosing an appropriate model for your business • Exploring ways to simplify content migration • Realising how your CMS can impact on user experience • Getting your CMS to be fully accessible • Brief case study

  8. Content migration • The simplest way of all is to start from the beginning • Clean slate • Opportunity to review site goals and architecture • Every piece of content is reviewed before migration • We always recommend this, it is sometimes done

  9. Can automate a migration • Needs considerable preparation • Must be tailored for each site migrated • Can be done for inconsistent quality content • Ideally still requires a human to view and approve migrated content • New site and old site have same structure

  10. Automated conversion • Clean up content • non-compliant file names • non-standard HTML code • orphaned files • empty directories • charset • XHTML 1.0 • abbreviations and acronyms • Convert to CMS templates • Import converted content into CMS • Review content and publish

  11. pstagg$ ./html2cms-cleaner /web/test/ Back-up the directory (Y/N)? y Backing-up: '/web/test' --> '/web/test-cleaner-bak'. File/folder expunging started... File/folder expunging completed! File/folder name cleaning started... File/folder name cleaning completed! File laundering started.............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................. File laundering completed! Expunging orphaned files started... Expunging orphaned files completed! Expunging empty directories started... Expunging empty directories completed! Finding local broken links started... Finding local broken links completed! File/folder flagging started... File/folder flagging completed! Finalising reports started... Finalising reports completed! Done & Dusted!!! pstagg$s Total Files Before = 13491 Total Folders Before = 734 Total Html Files Before* = 5166 Total Files After = 3865 Total Folders After = 416 Total Html Files After* = 1583 Orphaned Files = 9242 Orphaned Exceptions = 24 Renamed Files = 7839 Flagged Files = 1091 Expunged Files** = 9404 Expunged Folders** = 318 Updated Links = 4814 External Links = 2570 Broken Links = 617

  12. Best of both worlds? • Design new intranet • Build site architecture in CMS • Convert old content that will be migrated • Import relevant content into the new architecture (may require manual import)

  13. Utilising a Content Management System • Choosing an appropriate model for your business • Exploring ways to simplify content migration • Realising how your CMS can impact on user experience • Getting your CMS to be fully accessible • Brief case study

  14. Intranet CMS user experience • Desired outcome/experience may be the very different to that required for a public site • Want to encourage collaboration and participation, may allow any user to publish • Want seamless experience of web content and other applications/processes

  15. Intranet CMS user experience • Ease of creating/updating content • Familiar interfaces • Training implications • Integration with existing systems and processes • One more thing to remember?

  16. Utilising a Content Management System • Choosing an appropriate model for your business • Exploring ways to simplify content migration • Realising how your CMS can impact on user experience • Getting your CMS to be fully accessible • Brief case study

  17. Accessible CMS inputs and outputs • Policies and standards • Management support? • Contributor education • Templates • Controlled environment eg corporate browser and SOE standards • Vendor education • System safeguards?

  18. Utilising a Content Management System • Choosing an appropriate model for your business • Exploring ways to simplify content migration • Realising how your CMS can impact on user experience • Getting your CMS to be fully accessible • Brief case study

  19. South Africa campus London centre Parkville campus Snapshot of Monash • Over 50,000 students from more than 100 countries • 8 campuses: Australia (6), Malaysia and South Africa • Centres in Italy and United Kingdom • Several study modes • Pathway programs • Thriving community • 10 faculties

  20. Internationally-recognised research • International reputation in leading-edge fields • $27 million for NHMRC* research programs and projects (2005) • Australian Synchrotron (2007)and National Stem Cell Centre • 75 specialist research institutes/centres • 17 cooperative research centres • More than 2,400 academic staff publish some 5,000 articles annually • Global collaborations with more than 110 institutions *National Health and Medical Research Council

  21. CMS project • Commenced in 2002 – now mature. All faculties and almost all admin areas are CMS users. • Goals might be different now if we were starting out • Initial focus was on managing public sites

  22. Selected • TeamSite • MetaTagger

  23. Monash web strategy . . . Separate public content from internally focused content

  24. Monash web strategy . . . • Target content to user needs, roles and tasks

  25. Monash web strategy . . . • We had basic strategy and building blocks (CMS and portal) • We proposed a project to develop a university intranet based around these technologies • It was rejected. We have proposed it from several perspectives to no avail. • So we have started very small …

  26. Monash intranet ‘project’ • Find 2 or 3 early-adopters • Integrate CMS and portal • Implement a trusted authentication process • Usability evaluation and re-design of early-adopters intranets • Migrate early-adopters to new environment • Develop ‘desktop’ module for portal

  27. Next steps • Orderly queue of intranet and CAS clients • In-line editing of intranet content for authorised users • Student intranet project Sue.Steele@its.monash.edu.au

More Related