Bulletin Board - Document Comments

Bulletin Board - Review and Comment

Step 1 of 4: Comment on Document

How to make a comment?

1. Use this Protected Document to open a comment box for your chosen Section, Part, Heading or clause.

2. Type your feedback into the comments box and then click "save comment" button located in the lower-right of the comment box.

3. Do not open more than one comment box at the same time.

4. When you have finished making comments proceed to the next stage by clicking on the "Continue to Step 2" button at the very bottom of this page.

 

Important Information

During the comment process you are connected to a database. Like internet banking, the session that connects you to the database may time-out due to inactivity. If you do not have JavaScript running you will receive a message to advise you of the length of time before the time-out. If you have JavaScript enabled, the time-out is lengthy and should not cause difficulty, however you should note the following tips to avoid losing your comments or corrupting your entries:

  1. DO NOT jump between web pages/applications while logging comments.

  2. DO NOT log comments for more than one document at a time. Complete and submit all comments for one document before commenting on another.

  3. DO NOT leave your submission half way through. If you need to take a break, submit your current set of comments, take a note of where you up to and return later to make a further submission.

  4. DO NOT exit from the interface until you have completed all three stages of the submission process.

  5. If you would like a copy of the comments you made via the Bulletin Board, please email policy@rmit.edu.au and specify which document you provided feedback on and a copy of your submission will be emailed to you.

 

Web Development and Maintenance Procedure

Section 1 - Context

(1) This procedure provides a framework to manage the scale and makeup of RMIT’s web presence using its primary content management system. It ensures that new websites are planned, created and resourced as part of an enterprise-wide web strategy and that RMIT’s web presence adheres to brand, web standards, cyber-security, regulatory and legal requirements. 

Top of Page

Section 2 - Authority

(2) Authority for this document is established by the Brand and Communications Policy.

Top of Page

Section 3 - Scope

(3) This procedure applies to all staff who want to create websites, including mobile websites and mobile apps, as part of the RMIT’s web presence. It also includes existing off-platform sites as well as website redesigns and the procurement of URLs, hosting providers and third-party web publishing platforms.

(4) This procedure does not apply to:

  1. courseware, including scholarly work, student work and learning and teaching materials;
  2. databases and systems presented via a web interface (e.g. library records, Canvas, Archibus);
  3. sites with an approved business case confirmed via procedure;
  4. agreed business entities.
Top of Page

Section 4 - Procedure

(5) RMIT will develop, maintain and manage its website in a manner that will ensure:

  1. a consistent design applied across all RMIT Group webpages, adhering to the RMIT brand;
  2. users have access to content relevant to their needs;
  3. information on each page is current, accurate and meets accessibility standards;
  4. information on each page complies with relevant legislation, international standards and RMIT policy.

Site Hosting

(6) RMIT uses select content management systems for the publishing of websites on approved hosting providers. These are contained under the domain rmit.edu.au. 

(7) All website publishing is to take place using RMIT’s approved content management systems and hosted through approved hosting services.

(8) New sites will be created within the framework of RMIT’s existing web infrastructure. 

(9) The primary content management system is:

  1. Adobe Experience Manager – approvals managed by the Vice-President, Engagement their delegate for use for all official RMIT channels including but not limited to public facing websites (including information for prospective students, current students, researchers, industry partners and alumni), and staff facing websites; 
  2. If required, Campus Press – approvals managed by the Vice-President, Engagement their delegate. For all non-official but adjacent channels such as staff web presences and research that are not associated with formal research groups or entities. These pages are hosted under the subdomain sites.rmit.edu.au. 

(10) To create a site ad its URL are not being actively maintained, the Digital and Experience team will work with the Chief Information Security Officer’s team to retire the unused URL. 

(11) New domains and subdomains need to be signed off by the Vice-President, Engagement or their delegate to ensure URLs for subdomains are consistently implemented across RMIT. 

  1. Where a site and its URL are not being actively maintained, the Digital and Experience team will work with the Chief Information Security Officer’s team to retire the unused URL.

Site Hosting

Requesting Permission

(12) Requests for permission to use an off-platform site must be supported by a business case submitted to the Digital and Experience team. The business case for off-platform sites must show how an agreed and material functionality is not available on the existing Adobe Experience Manager platform or Campus Press platform. 

(13) Off-platform sites must also complete:

  1. Cyber Security Risk Assessment (SRA);
  2. Privacy Impact Assessment (PIA).

(14) If approved, the following must be registered on the ITS Configuration Management Database, so continuity of access is maintained. 

(15) Staff in breach of the Brand and Communications Policy will be required to hand over sites to the Digital and Experience Team for assessment. 

Requirements of Off-Platform Sites

(16) Off-platform websites must:

  1. adhere to brand guidelines;
  2. adhere to accessibility standards;
  3. be presented in a format suitable for online delivery;
  4. use existing functionality (where it exists) to avoid duplication;
  5. ensure currency and consistency of information and management processes;
  6. be created based on customer-centric principles, be directly relevant to the intended audience, be structured in a way that optimises the audience journey and support achievement of business goals; 
  7. align with RMIT’s strategy and associated business goals.
  8. be presented in a user-friendly manner;
  9. receive an appropriate level of authorisation for text, imagery and video prior to publication;
  10. be reviewed and maintained in line with business lifecycles, and when no longer required, removed to ensure accuracy, relevance and currency;
  11. meet RMIT’s high standards of quality assurance;
  12. not publish the personal information of staff, students, or others without their prior written consent.
Top of Page

Section 5 - Compliance

(17) The Vice-President Engagement reports breaches of the Policy to the University Executive Committee bi-annually. 

(18) Breaches of this procedure are reportable via the Organisational Breach Reporting Form and are managed in accordance with the Compliance Breach Management Procedure.    

Top of Page

Section 6 - Definitions

(19) Defined terms below are specific to this policy.

Term Definition
Content management system Software that helps users create, manage, and modify content on a website.
Database An organised collection of data stored and accessed electronically.
Domain A subset of the internet with addresses sharing a common suffix or under the control of a particular organization or individual. E.g. rmit.edu.au.
Off-platform A website that is not built on RMITs Adobe Experience Manager or Campus Press content management systems.
On-platform A website that is built on RMITs Adobe Experience Manager or Campus Press content management systems.
Subdomain A subdomain is a domain that is a part of another domain, e.g. openday.rmit.edu.au.
Web Presence A location on the World Wide Web where RMIT is represented.