Changes

Created page with "== Web Priorities Notes - Sep 18, 2024 == === Updates === '''DTO''' *We are working on pushing out the topic page guidance. It is currently available in GC web and AEM *Topi..."
== Web Priorities Notes - Sep 18, 2024 ==
=== Updates ===

'''DTO'''
*We are working on pushing out the topic page guidance. It is currently available in GC web and AEM
*Topic page working example: [https://wet-boew.github.io/GCWeb/templates/topic/topic-en.html [Topic title] - Canada.ca (wet-boew.github.io)]
*Page de sujet exemple pratique : [https://wet-boew.github.io/GCWeb/templates/topic/topic-fr.html [Titre du sujet] - Canada.ca (wet-boew.github.io)]
*Topic page GCWeb documentation: [https://wet-boew.github.io/GCWeb/templates/topic/topic-doc-en.html Topic page - Canada.ca (wet-boew.github.io)]
*Page de sujet documentation de GCWeb : [https://wet-boew.github.io/GCWeb/templates/topic/topic-doc-fr.html Page de sujet - Canada.ca (wet-boew.github.io)]
*AEM:
**[https://www.gcpedia.gc.ca/gcwiki/images/d/df/AEM-Documentation-6.5-Unit-3-13-Creating-a-Topic-Page.pdf Unit 13 – Creating a Topic Page (gcpedia.gc.ca)]
**[https://www.gcpedia.gc.ca/gcwiki/images/d/d0/Documentation-AEM-6.5-Unite-3-13-Creer-une-Page-de-sujet.pdf Unité 13 – Créer une Page de sujet (gcpedia.gc.ca)]
*First search working group happened yesterday. Will be meeting again in two weeks.

'''PCO'''
*Let us know if you have any promotions for October
*Engagement with MOs about advertising
**If you get inquiries about adjusting advertising, please let us know so that we can coordinate

'''CDS/DTO - Research roadmap - GC Design system'''

'''Research plans'''
*The GC Design System
**Made of building blocks
**Unified experience
**Framework agnostic
**Alpha phase
**Full-time team working on it
*Agile system
**Building quickly and test often based on feedback
*Support products goals
**Common denominator assets
**Increase trust
*Research goals:
**Define risk clients see
**Define good metrics
**Understand the pain points
*Areas of focus:
**Accessibility:
***ensuring component accessibility
***Component usability
**We purchased Userlytics
***Interactions
**We launched a bilingual Figma library
**Journey
***Developer onboarding
**Relationships
***Feature requests
**Overall
***Developing product metrics
***Market research survey
**You can participate in the in the testing by contacting us: [https://design-system.alpha.canada.ca/en/get-involved/ https://design-system.alpha.canada.ca/en/get-involved/]
**You can also check the planning documents:
[ https://miro.com/app/board/uXjVKPAqeo8=/?share_link_id=340540641020 https://miro.com/app/board/uXjVKPAqeo8=/?share_link_id=340540641020]

'''Q&A'''

Q: About archiving best practices, any thoughts about this?

A: We’re not in TBS anymore, so not as connected to policy shops and we have reduced insight into this issue.

Q: What are the costs if we have to migrate from AEM?

A: At this point it’s premature to say, we are still working on the issues.

Q: Should we be using trigger warnings for sensitive content?

A: Can you give us some context.

*Example, residential schools, sensitive issues such as that

DTO comment: There is a lot of research pro/con, but we would have to examine it more closely before giving any guidance


=== Roundtable ===

'''PSPC'''
*Working on Indigenous procurement campaign for late October launch