If You can request a publishing queue if your Single Digital Presence site (is hosted on http://content.vic.gov.au/) meets the below criteria, you can request a federated publishing queue and your team:
provides web content that looks after for a distinct audience group (not an organisation)a dedicated digital team with
looks after more than 200 pages
has, or will have, at least 2 digital specialists (at least minimum 2 years' previous experience each)
ownership of more than 200 pagescommits to maintaining content and reporting annually on content performance.
| Info |
|---|
Once implemented, designated approvers will be able to manage the publishing and archiving of information on vic.gov.au via their own publishing queues in Jira. Approvers are responsible for auditing content to ensure it making sure all content follows the Victorian Government style guide and meets digital accessibility requirements, and for measuring content performance. |
Steps to get your publishing queue running
Seek approval from your parent department’s central digital content team. They may require further approvals, such as from your department’s digital management committee.
Email the Single Digital Presence team at digital@dpc.vic.gov.au with your The lead approver in your organisation should submit an SDP support request for a publishing queue and details of who provided the approval.
The Single Digital Presence team will reach out with questions to confirm your eligibility.
If approved, nominate queue approvers that will manage your publishing queue and ask them to complete the approver readiness program on the Innovation Network (only accessible to VPS employees).Once you have at least 1 trained publishing queue approveryour 2 digital specialists to complete the publishing queue training which will give them publishing permissions in the CMS. If your 2 nominees have not already completed editor training, they’ll need to request a Vic Gov CMS account and complete editor training first.
The SDP team requests the setup of a Jira project and Jira accounts for the approvers so they can process tickets in their queue.
Once your 2 digital specialists have completed the approver readiness program, your queue will be turned on.
Content that is saved as ‘needs review’ by a user with your department or organisation assigned in their ‘department’ field in their settings will be directed to your queue to be reviewed
Workflow for federated publishing
When a user saves a page with the status ‘needs review’ or ‘archive pending’, this triggers a Jira ticket to be created.
Our Jira ticketing system has logic that directs the ticket to the relevant publishing queue (Jira project) and subqueue based on the users ‘department’ field in their CMS user account and the page’s site or site section.
Related resources
Publishing pages on vic.gov.au | Victorian Government (www.vic.gov.au)
How our publishing workflow works | Victorian Government (www.vic.gov.au)Approver readiness program | Innovation Network (only accessible to VPS employees)