• What is Drupal?

    Drupal is an Open Source content management system (CMS) for websites that will be replacing the UQCMS platform.

    The UQ Drupal Transition Team have been working hard customise Drupal 7 to create a flexible yet simple platform for organisational units to use in managing their web presence, while still adhering to UQ styles and branding.

  • What is the history of UQ Drupal?

    UQ-Drupal pilot was originally conceived and architected by Stuart Rowlands and David Gwynne (EAIT) in 2011. After the assesment of various web building paltforms, Drupal became the choice as successor to the ageing OCMPS platform.

    The UQ-CMS replacement project is underway to phase out the old platform by late 2016.  

    The UQ Drupal core has been contributed to since 2011, in particular by the following people in it's early form: 

    • Core development & systems architecture: Stuart Rowlands & David Gwynne
    • Central data architecture & development: Stuart Rowlands, Jim Smith & key input by David Gwynne
    • Display suite inception development: Stuart Rowlands
    • Core theme development: Graham Arrowsmith & David Pollitt
    • Core contributors: Graham Arrowsmith, Jim Smith, Jonathan Matthew
    • Training materials: David Pollitt & Donna Clark, Deborah Roberts
    • Initial conception of the Migration Script: Stuart Rowlands
       

    The expanded UQ Drupal Team is now working working on bringing UQ Drupal, support and training to the University.   We would also like to say a special thanks to the early adopters for all their feedback and support in helping build the platform.

  • Are there any UQ sites in Drupal?

    There are currently over 100 sites in UQ Drupal. Take a look at this site regularly to check the latest sites to be built. 

    A few of the centrally-supported sites are:

    There are other sites in UQ Drupal who were the early adopters using their own Drupal capability, and are not centrally supported.

    Several areas of UQ were already using Drupal before it was selected as the UQ-wide solution, so there are already many UQ websites running on Drupal. These areas are running their own versions of Drupal, not using the forthcoming central system.

  • How can I get a UQ Drupal site?

    There are 2 main options for getting a UQ Drupal Site:

    • Use the Panel of Preferred suppliers - Please contact Dee McGrath, CMS Transition Manager for information on UQ approved suppliers.
    • 1:1 Migration (Tier 1 OCMPS Sites only)

    We understand that areas across the University are eager for a better web solution, and we are too. However, we want to make sure that this system will be reliable and easy to use, with features that will let UQ organisational units be more self-sufficient and create better websites.

    The CMS Transition team has identified the use of a technological 1:1 migration option for basic sites sitting on the OCMPS platfrom. These Tier 1 sites have little, or no reliance on Central Data, and are typically very small (less than 20 pages). There are aproximately 120 sites that have been assessed as suitable for the automated process. The Migration Coordinator will assist the CMS Transition Manager to contact the Web Managers of the Divisions and Faculties across UQ to build a roadmap, and process these migrations - beginning mid-November 2014 onwards. It is envsioned that inline with further development on Central Data, mid sized sites (Tier 2) may also be suitable for a migration process. This process does not include any site architecture or design changes (some legacy CSS may be lost in the update). It's is 1:1 for content, with the new UQ Drupal CMS back-end and hosting. Each home page will need to edited by hand.

    The transition steering committee is also undertaking a further prioritisation and some rationalisation of UQ’s Web presence of over 700 sites. Sites will be prioritised by UQ’s business needs, site traffic analytics, those on the old CMS platform (OCMPS), organisational readiness, use of central data and complexity. The transition will be firstly focused on sites that improve the student experience, which includes Future Students. This prioritisation will designate the next 50 sites for transition. Smaller sites, such as project websites and individual event sites, may be directed to Self Starter sites, or scheduled for late 2015. 

    The CMS team are currently working on transitioning the School sites during the later quarter of 2015, while Web Services focus on the Future Students Portfolio and continuing work on my.UQ. 

    We recommend those not in the top 50 or Tier 1 or 2,  hold off developing their sites until around the first quarter 2016, to take advantage of the features and central data that will be available at that time.  

  • What are the roles in UQ Drupal, such as Site Editors and Site Coordinators ?

    These are different roles that are available by default in UQ Drupal. Most people editing the content on sites will be Site Editors. Please read more in the Help Guide.

    Site Editor Role

    (Included by default ) – updates content including adding / removing files and images, with potential limits on what they can edit or publish.

    Must complete online training

    Site coordinator Role (required)

    A site coordinator does basic site maintenance tasks and can do pre-defined customisations such as customising the home page layout. A site coordinator would typically also have content editing and user management responsibilities.

    Requirements/prerequisites:

    Must be able to demonstrate basic HTML/CSS knowledge (for applying UQ styles and troubleshooting content in the WYSIWIG editor)

    Must complete online training  

    Permissions on a site by site basis

    all permissions of a Site Editor, plus

    manages editor access, and assists them with editing tasks

    manages updates to significant content such as the home page and top menus

    creates and modifies menus 

    add and modify predefined configurable blocks

    can override default URLs

    Has access to site reports

    Web Manager (An oversight role, it is someone who has the say or access to sign off on what content goes on the site, and authorises and co-ordinates those working on the site)

    Site Architect/ Administrator (optional) – uses advanced Drupal functionality to customise content, pages and layouts of their site. Must have demonstrable Drupal specific developer skills.

  • I need a new site and it can’t wait until UQ Drupal is available. What should I do?

    If a new website is essential, there are several different options:

    • There is a Panel of Preferred external providers of UQ Drupal services available. Please contact Dee McGrath, Transition Project Manager for details.
    • You can make arrangements with external providers to create your site outside of UQ Drupal, and UQ Hosting, and then arrange at a later date to re-create the site within UQ Drupal if you wish.
       
  • How long will UQCMS remain available?

    Although UQCMS is an old system with many limitations, there is no requirement for you to move your sites off OCMPS in 2015 if you are not ready or have an overly complex site.

    We will continue to fully support existing OQCMS sites in 2015, but Web Services will no longer create new sites in UQCMS.

    We plan to gradually step down support for OCMS during late 2015 and decommission the CMS and related hosting during 2016. Any updates to this date will be available on this site. After this date, sites will become read-only / decommissioned. Your Web Manager will be contacted about any site decommisions. 

  • Planning a new website in Drupal

    Whether you are creating a new DRUPAL website, or migrating a UQCMS website to DRUPAL there are a number of key steps to follow in this process before your website goes live.

    Now is also a good time to identify and audit all the websites belonging to your area. Determine your priorities for transition, and look for opportunities to consolidate multiple websites into fewer sites in UQ Drupal. Identify and delete redundant, outdated or trivial content. Consider what Central Data you can use or submit (saving you time in recreating it). Start decommissioning any sites that aren’t worth the effort of bringing over to Drupal. Faculties will work with their schools and other organisational units to internally prioritise their transition.

    Begin budgeting for the move. 

    Before Drupal is ready, the main thing you can do is consider what the future of your area’s websites and web operations should be: What is your audience looking for? Where do they expect to find it? What is their user experience of your site withing UQ's web presence. What websites will you need? How do you want your part of UQ to work together on websites? How much capability do you need to build?

    There is a step-by-step guide on planning your website in Drupal that we recommend users familiarise themselves with before commencement of their website project.

  • Where can I find more information?

    Information sessions will be scheduled once the transition roadmap is finalised. They will be open to anybody who is interested in finding out more about UQ Drupal. This website will also be updated as information becomes available. Please contact Dee McGrath, CMS Transition Manager for more information.  Training is available on this site for the standard template and the newer school template. 

    Significant updates will be included in UQ Update.

    If you’d like to try Drupal for yourself, you can create a temporary sandbox site.

    If you would like to discuss your web presence in more detail, contact Dee McGrath on uqdrupal@uq.edu.au