Update new styles & URLs
Instructions to update to the new branding styles
The Drupal environment at ANU is complex. There are many factors that influence a style rollout including:
- Separate instances of Drupal
- Different versions of Drupal
- Use of independent servers outside of the main ANU web server
- Use of modules/theme outside of ITS built and supported components
- Use of in-line styling
It is because of these challenges, that a staged approach to implementing the new webstyles is required.
Process for updating:
- Review the style guidelines to become familiar with the new elements.
- Raise a ticket in Service Desk to indicate you are interested in converting your website to the new identity. Please include a link to your website for reference. Please note: Due to the number of websites within the ANU environment, any new requests for ANU identity support will be subject to a prioritisation process for MSRD/ITS assistance.
- Receive confirmation from MSRD/ITS that your website is good to proceed.
- Create a dev site by cloning your production site into a development environment.
- If you require a new dev site, please raise a Service Desk ticket for the Unix team.
- A dev site is required to provide you the opportunity to see how universal style changes will affect your site before you go-live.
- It will also help identify situations (pages, buttons, boxes) which have not been changed by the universal styles deployment. This can result from in-line styles that have been used, or anything specific to your website that isn’t in the Gateway site. Anything that remains unchanged will require manual adjustments.
- Once you have a dev site, and assuming you are using the current central acton theme, point your dev site to the new style server:
- Login to your dev site
- Go the Appearance -> Acton site profiles and change the URL to point to https://bootstrap-dev.anu.edu.au/_anu
- Flush the site cache by clicking on “Configuration > Performance"
- Click on “Clear all caches”
- If you don’t have access to change these settings, please let us know. You should immediately see changes to your dev site after following this process.
- Alert MSRD that you are now pointing to the new style server as a comment in your original Service Desk ticket.
- You must review your entire site to identify any pages that require manual implementation of the new style. This can occur where in-line styles or custom layouts have been used.
- It is strongly recommended that you keep a record of all URLs that require a manual change, what the change is, and the process to fix it.
- Download tools to your browser to check for Web accessibility (AA).
- After AA checks, alert MSRD that you are now pointing to the new style server as a comment in your original Service Desk ticket.
- FOR COLLEGES WITH NO WEB SUPPORT: Submit your manual fixes list to MSRD for review in order to assess the amount of support required to move the styles onto your live website. MSRD will provide a timeline for this.
- Once you have reviewed your site, and are comfortable with the manual fixes required, alert MSRD to provide a final review.
- To complete the go-live process, replicate all the manual fixes on to the live site.