869
edits
Changes
Jump to navigation
Jump to search
Line 7:
Line 7: − + − *The typography specs areː − English: https://design.canada.ca/styles/typography.html\ − French: https://conception.canada.ca/styles/typographie.html+ − *The social media channels pattern in GCWeb has been updated to reflect the new Twitter/X logo, but there’s no set deadline to make the changes. The change has been automatically in AEM.+ − *Reminder our email has changed, our old forwarding email is not active anymore+ − *New email: [mailto:Cds.dto-btn.snc@servicecanada.gc.ca cds.dto-btn.snc@servicecanada.gc.ca]+ − *Roundtable+ − + − *Release went through this week on changes to Institutional Landing Page Template that DTO discussed+ − + − **Update to the bold class for the news feed+ − **Logo change: Twitter to X+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + − *International Women's Day 2024 theme and toolkit are now live: [https://women-gender-equality.canada.ca/en/commemorations-celebrations/international-womens-day/2024-theme.html (https://women-gender-equality.canada.ca/en/commemorations-celebrations/international-womens-day/2024-theme.html)] − '''Service Canada''' − − '''[[:en:images/c/cf/Dental_care_plan_case_study_-_PFT-_ENG_for_posting.pdf|Presentation: Using page feedback to improve the Canadian Dental Care Plan]]''' − Canadian Dental Care Plan case study: Iterative approach+ − *December 2023 - Published content on web − *We included page feedback tool, for 8 pages of English, and 8 pages of French content − − *Many issues identified in first week, period with highest amount of feedback − *4 post launch reports at different time periods − *We manually tagged and sorted comments, 800 comments − *Summarized top issues, provided recommendations for improvements − *Reports were more detailed as time went on − *Four big issues:+ − *#Birth date calendar picker was hard to use to determine when to apply − *#*So we simplified the way the calendar worked − *#*We also gave users the choice of using the tool, or using a text chart to enter their information − *#Children’s dental benefit alerts reduced the scent of information for seniors − *#*64 comments in first 24 hours from seniors who were confused if the program was for them, they were thrown of by the information about children − *#*We added the text “starting with seniors” which helped and negative feedback decreased right away − *#Adjusted family net income terminology confuses single seniors − *#*The term is confusing − *#*We improved the navigation to make it more clear where users should keep clicking, avoiding specific eligibility criteria on navigation pages − *#*We also added expand and collapse to define eligibility criteria − *#Policy for eligibility confusing: what if someone has partial dental coverage − *#*This became a big issue, even internally the answer was not fully known − *#*We grouped the questions from users we got and shared them with policy makers − *#*In addition, media raised the issue which raised visibility − − *Guidance in WET could be updated to help people with date picker calendars − *It would help GOC web community to have discussion around when is best time to introduce eligibility criteria − *Shared top policy questions with policy partners from the two departments − *Worked with call centers to determine if answers were coming from other actors − *That users questions are extremely valuable, to alert policy makers to problems with programs/policies − *Brings up the interesting idea of crowd-sourcing for ideas − *Reduce risk by audience testing, read and analyze feedback, share with partners − '''Questions:''' − Q:Where is the best place to post about eligibility requirements?+ + − A: The main point is that the help has to be interactive. This is what we’ve learned from testing.+ − Q: For CRA , we have to go all the way up the approval chain. Was your approval process for this project fairly agile?+ − A: Setting up the approval process, and a warning before it launched that there would be the need for approvals and iterative changes right away. We were clear with our senior leaders what the iterative approach meant, that there would be a need for quick approvals. We were able to get buy-in from senior management which was key. + − '''[[:en:images/4/47/AB_Testing_of_Alert_styles_&_impact_on_IRCC_Secure_Account_page_ENG_for_posting.pdf|LISA FAST - AB testing with IRCC]]'''+ − − *We did an A/B test with what was on the website, and other kind of warnings − *We discovered that on mobile an icon was missing − *The warning worked better than the alert band, especially in mobile − *So we moved on to test 2 − *The band as designed on the live site is doing a good job − *However, we consistently saw differences between the desktop and mobile, which isn’t supposed to happen − *Test 3: Alert band vs warning alert vs contrast band − **Contrast band had more conversions − **Unfortunately it distracted from other content on the page which was more important − '''Takeaways:''' − *Contrast design is too noticeable − *Standard warning alert should be placed before important content − *Warnings/alerts are more distracting on mobile…so if your page is really popular on mobile, be careful you don’t overuse them − *Warnings imply that something has changed, something has just happened
April 10, 2024 - Updates, priorities of the week (view source)
Revision as of 09:28, 3 May 2024
, 3 Mayno edit summary
=Notes and action item=
=Notes and action item=
===DTO update===
===DTO update===
*We are updating the new main page title style (H1). It has been rolled out in AEM and is available in the latest release of GCWeb. The main heading styles will be automatically updated when you upgrade to the latest version. It should be available via CDTS, Drupal WXT and the GC design system by mid-March
*CRA presentation postponed to May 1
'''PCO'''
* Budget is launching April 16, 4pm
** One hour AEM newsroom pause 3:30-4:30pm
** Blackout is for AEM newsroom items only
'''Principal Publisher'''
** Stay tuned, more details next week
** If you are looking for specific answers, talk with your internal comms colleagues, they are your first point of contact
**Update to the main page title (h1) style
* April promo updates coming up in April
** One about measles coming soon from Health Canada
* If you have questions about WET, they have office hours on Tuesdays, more details here: [[/github.com/wet-boew/wet-boew/wiki/WET-Office-hours,-Heures-de-service-de-la-BOEW|https://github.com/wet-boew/wet-boew/wiki/WET-Office-hours,-Heures-de-service-de-la-BOEW]]
=== Discussion ===
The méli-mélo feature in WET is unstable and some participants mentioned that they would like it to be more stable. There were many issues with pages “breaking”.
Others said it was meant to be experimental, but the argument was made that the experimental period was taking too long.
The fact that a lot of web design elements are not funded was discussed, and many agreed that this was a problem that hampered forwarding the work.
DTO replied:
This is how WET is managed today, but changes are coming. Eventually we will be discussing the GC Design system rather than WET. We are hoping that changes will be more efficient in the new system that is coming.
Timelines
Alpha project is available and you can experiment with it now. We anticipate it will be in alpha mode for several months. We will be coming out with more information for the community about the changeover from WET to GC Design system in the coming weeks.
Question section (Ask me anything)
How does the information get disseminated to the developers through the community? For example our team was going to switch to Drupal, and they had no idea that the GC Design System was coming.
DTO Answer:
Our hope is that the Web teams at departments are conduits to educate their colleagues. So this meeting is one of the main communication tools.
Follow up to all participants:
If anyone has guidance documents for synching up comms and tech staff, please forward it along to: [[Mailto:Abigail.Hambly@tpsgc-pwgsc.gc.ca|Abigail Hamley]]
Question:
About the topic template, all of our content needs to be updated to new templates. Is it a good time to update, should I wait?
Answer:
We talked to Principal Publisher about timelines for making the Beta pattern into the default pattern. This should all be stabilized by the end of this fiscal year. So you can go ahead and use the Beta versions that are available right now.
Comment:
Next Monday we’re discussing accessible POWER Bi dashboards on the web. Sign up at this link if you’re interested: [[/events.teams.microsoft.com/event/da6851d0-d919-4d16-9e45-1f23a285d1ab@9da98bb1-1857-4cc3-8751-9a49e35d24cd|https://events.teams.microsoft.com/event/da6851d0-d919-4d16-9e45-1f23a285d1ab@9da98bb1-1857-4cc3-8751-9a49e35d24cd]]
DTO:
It’s clear that we need more follow up on this issue, to find out exactly what happened, how much of an effect it has had on pages, on how to rectify the problems. We’ll be working on this in the coming days.
Question:
Based on the discussion, I’m assuming that a lot of the groups are under AEM. My team uses Drupal. We can’t easily update our H1, will there be a fix in Drupal for this? We are getting pressure from our senior management.
Answer:
The WXT team has a ticket on this issue. We can share the ticket with you to give you more details about it so you can share it with others in your department.
Question:
The Canadian General Standards want to do consultations. Is there a move to a general system for consultations? Or should we just build our own system?
Answer:
No, at this time, there’s no move for a standardized system. There has been work on this in the past but it hasn’t led anywhere. Suggest you reach out on Slack, because many departments have done this kind of work.
Question:
Is there a plan to pivot from the current “non funded” web framework to a well funded digital focus that supports building better digital services.
Answer:
In summary, that's the plan with the GC Design System. You can check out the alpha version: [[/design-system.alpha.canada.ca/|https://design-system.alpha.canada.ca/]]
We can suggest that you connect with the CDS platform team to help with the development of the new system.
=== Roundtable ===
'''ECCC'''
* New CCR estimates tool is now live: [[/www.canada.ca/en/revenue-agency/services/child-family-benefits/cai-payment/how-much.html|https://www.canada.ca/en/revenue-agency/services/child-family-benefits/cai-payment/how-much.html]]
'''WAGE'''
'''WAGE'''
* We migrated to AEM this week, here are the new URLs: [[/www.canada.ca/en/women-gender-equality.html|https://www.canada.ca/en/women-gender-equality.html]]
*We analyzed feedback to make quick iterative improvements according to comments, this was a game-changer
'''DND'''
'''LESSONS LEARNED'''
* New defense policy released on Monday: [[/www.canada.ca/en/department-national-defence/corporate/reports-publications/north-strong-free-2024.html|https://www.canada.ca/en/department-national-defence/corporate/reports-publications/north-strong-free-2024.html]]
* Also new content for [[/www.canada.ca/en/air-force/campaigns/2024-centennial.html|Air Force Centennial]]
'''PSPC'''
* PSPC is continuing our migration to Canada.ca. We'll be undertaking an optimization project for Pay content this spring.
'''DTO'''
* The Gen AI Chatbot Collaborative Working group kickoff meeting is being planned for next week to review the draft guidance - in case anyone here is unaware of the Chatbot channel on GC Comms Slack and wants to add someone to the group or just follow along.
*Looking to understand the use of the alert band
