Important: The GCConnex decommission will not affect GCCollab or GCWiki. Thank you and happy collaborating!
December 14, 2022 - Updates, priorities of the week
Back to GC Web Priorities Meetings - Réunions des Priorités Web du GC
Meeting information
Agenda
1. Updates
2. Roundtable
Notes and action items
Privy Council Office (PCO)
Met this morning about housing. Prototype started. Lots of departments involved, including ISC, ISED, CMHC etc.
Remember to adjust pace for the holidays, take a pause where you can.
Canada School of Public Service (CSPS)
Accessibility content going live on December 20
Royal Canadian Mounted Police (RCMP)
David Calaam had a question about hosting audio on SoundCloud, similar to hosting video on YouTube. Can we share a soundcloud audio clip on our website? Discussion to be moved to Slack as no answer currently.
Digital Transformation Office (DTO)
Footer guidance is live on design.canada.ca, all the footer pieces are broken out there: Global footer - Canada.ca design system
● GCweb (WET) implementation reference links are in the How to implement section
● Principal Publisher is also preparing detailed instructions for AEM and will be reaching out to anyone who currently has a contextual contact link to walk them through how to add the contextual band
● CDTS and Drupal implementation references are in the works - likely ready by mid-January
We need to figure out the process to get people to apply the footer. We would like to come up with a target date to get most people to switch over but we want that date to be realistic. This is what we have came up with currently:
Phase 1: December
Published guidance, GCWeb code is live
This phase is for you to explore the guidance, look at the code, come to us with questions. We still need to get the code to the centrally deployed template system (CDTS) and in Drupal
Phase 2: December/ January
Start thinking about implementing, do you need a contextual band, do you need to create pages for the contextual band to link to. Work with your IT teams to figure out their needs. Are there other things you need from us to make this work for you?
Phase 3: target timeframe TBD
We want to aim for an implementation window of approximately 1 week or where the majority of institutions can implement the new footer at the same time. From discussion, possibly sometime in February, to give time for CDTS and Drupal support to be ready.
We acknowledge that this won’t all happen the same day but are trying to do it within weeks, not years.
Principal Publisher will still reach out to those with contextualized footers. This should happen in the next few weeks.
If you have questions as you look through the guidance and the code please reach out to us. We have a Slack channel about this topic here:
Task Success Survey (TSS)
Task Success Survey presentation
Leadership in departments needs to carve out time for their teams to work on improvement.
What we’ve learnt from DFO so far:
- Realized TSS wasn’t running across all subdomains, fixed that
- ‘Other’ was coming in as the top task, so we clarified the wording at the first and second levels, and added examples
- Since November we have seen a 50% reduction in people using ‘other’ as a response
TSS is a good place to start with continuous improvement projects.
DTO can still provide support for analyzing data and identifying tasks to improve in Q4.
Accessibility plans and templates
Documentation coming soon to accompany the templates. Will be in the same place as the templates:
There has been a request to be able to submit attachments via the feedback form. We’ll take this away and look at it
Question about whether AEM can configure different acknowledgements (as the email feedback form has different ones depending on if someone submits their email address or not). Principal Publisher will take this away and look at it.
