canada-ca / blogue-canada-ca-blog Goto Github PK
View Code? Open in Web Editor NEWCanada.ca blog: Digital Transformation Office | blogue de Canada.ca - Bureau de la transformation numérique
Home Page: https://blog.canada.ca
License: MIT License
Canada.ca blog: Digital Transformation Office | blogue de Canada.ca - Bureau de la transformation numérique
Home Page: https://blog.canada.ca
License: MIT License
Describe the bug
Dates on French home page are displayed in English
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A long string date in French should display the name of month in French
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
{% assign m = page.date | date: "%-m" %}
{{ post.date | date: "%-d" }}
{% case m %}
{% when '1' %}janvier
{% when '2' %}février
{% when '3' %}mars
{% when '4' %}avril
{% when '5' %}mai
{% when '6' %}juin
{% when '7' %}juillet
{% when '8' %}août
{% when '9' %}septembre
{% when '10' %}octobre
{% when '11' %}novembre
{% when '12' %}décembre
{% endcase %}
Describe the bug
All pages should specify a valid canonical URL to get more control over how duplicate URLs are treated by search engines. When a set of URLs on our site return duplicate or near duplicate content, search engines will select a single definitive URL for that content called the canonical URL*. This URL will be crawled more often, will take priority in search results over URLs with duplicate content and search rank boosting backlinks to the URLs with duplicate content will be viewed as linking to the canonical URL.
To Reproduce
(English)
Visit Canada: Optimization - Canada.ca
blog.canada.ca/2018/03/29/visit-canada-optimization/
(301 ) Visit Canada: Optimization - Canada.ca
blog.canada.ca/2018/03/29/Visit-Canada-Optimization/
Canonical URL redirects
Canada.ca is a trusted source - Canada.ca
blog.canada.ca/2020/08/10/canadadotca-trusted-source/
(301 ) Canada.ca is a trusted source - Canada.ca
blog.canada.ca/2020/08/10/CanadaDotCa-trusted-source/
Canonical URL redirects
Improving Canada.ca by focusing on COVID-19 top tasks - Canada.ca
blog.canada.ca/2020/09/24/covid-top-tasks/
(301 ) Improving Canada.ca by focusing on COVID-19 top tasks - Canada.ca
blog.canada.ca/2020/09/24/COVID-top-tasks/
Canonical URL redirects
(French)
Visiter le Canada : optimisation - Canada.ca
blogue.canada.ca/2018/03/29/visiter-le-canada-optimisation/
(301 ) Visiter le Canada : optimisation - Canada.ca
blogue.canada.ca/2018/03/29/Visiter-le-Canada-Optimisation/
Canonical URL redirects
Canada.ca est une source fiable - Canada.ca
blogue.canada.ca/2020/08/10/canadapointca-source-fiable/
(301 ) Canada.ca est une source fiable - Canada.ca
blogue.canada.ca/2020/08/10/CanadaPointCa-source-fiable/
Canonical URL redirects
Améliorer le site Canada.ca en se concentrant sur les principales tâches liées à la COVID-19 - Canada.ca
blogue.canada.ca/2020/09/24/taches-principales-a-la-covid-19/
(301 ) Améliorer le site Canada.ca en se concentrant sur les principales tâches liées à la COVID-19 - Canada.ca
blogue.canada.ca/2020/09/24/taches-principales-a-la-COVID-19/
Canonical URL redirects
Expected behavior
Note that *"self-canonicalizing" a page by setting its canonical URL to itself is both valid and useful as it can help eliminate potential duplicates such as when pages may be linked to with tracking URL parameters. To suggest the canonical URL for a page we can:
<link rel="canonical" href="...">
tag inside the page's <head>
tag (most common) orLink: <...>;rel="canonical"
header to the page's response headers.Google suggest giving absolute canonical URLs over relative ones. Search engines are likely to ignore our canonical URL suggestion if we:
Keep in mind that for exact duplicates we should consider if it is more appropriate to use 301 redirects over canonical URLs to consolidate duplicates instead.
Describe the bug
Page descriptions shouldn't be too long or too short. Long page descriptions will only be partially shown in search results and short descriptions are unlikely to be helpful to users.
To Reproduce
(English)
(French)
Expected behavior
Recommended page descriptions are between 100 and 320 characters.
This is a broken link.
Describe the bug
Configure page resources to have long caching times so browser caches will retain them for longer. The cache duration of each resource URL can be specified by either:
Expires
response header which specifies the point in time the response becomes stale such as Expires: Fri, 10 Aug 2019 20:00:00 GMT
ormax-age
directive to the Cache-Control
response header that specifies the number of seconds the response is valid for such as Cache-Control: max-age=3600
for 1 hour.To Reproduce
Expected behavior
If max-age
and Expires
are both used, max-age
takes priority. Recommendation is to set the cache time of page resources to at least 24 hours.
Is your feature request related to a problem? Please describe.
Add a friendly user interface for content creator to increase speed, efficiency and quality of content.
Describe the solution you'd like
Something like Prose.io with some GitHub workflow integration
Describe alternatives you've considered
Additional context
Add any other context or screenshots about the feature request here.
Is your feature request related to a problem? Please describe.
Pages and research summaries' url have a segment /pages/
that is superfluous.
Describe the solution you'd like
Add an underscore to the pages folder in order to be ignored during the url build stage.
Additional context
To follow the URL model described in the Canada.ca Content and Information Architecture Specification we should avoid superfluous words such as “to”, “the”, “a”, “an”, “by”, “for” (for example, “/apply-student-loan” instead of “/how-to-apply-for-a-canadian-student-loan”.
Describe the bug
Avoid using @import
in CSS files as this prevents parallel loading of CSS. Inside a CSS file, @import
can be used to include the contents of another CSS file by specifying a URL. This can be convenient but impacts download times because browsers can only start fetching the imported URL after the CSS file containing the @import
has been fetched.
To Reproduce
theme.min.css
wet-boew.github.io/themes-dist/GCWeb/GCWeb/css/theme.min.css (2 CSS imports)
Expected behavior
To get a page to load CSS files in parallel, we should instead add a <link rel="stylesheet" href="...">
tag for each of the CSS files we need to load to the HTML code of the page.
Is your feature request related to a problem? Please describe.
No analytics are set up on the blog
Describe the solution you'd like
Add Google Tag manager to manage AA and GA or any other tracking scripts.
Describe the bug
Protect against XSS attacks by enabling browser XSS safeguards. XSS attacks involve an attacker injecting code into a page that is being sent to users. Some browsers have built-in XSS protection that is enabled by adding X-XSS-Protection: 1; mode=block to the response header of each page. This setting will stop the page being rendered if the browser detects an XSS attack. Note that this should only be considered as a last resort defence against XSS attacks.
Steps to reproduce the behavior:
X-XSS-Protection headers: None
Expected behavior
Our site should be thoroughly reviewed and built with XSS safeguards in mind to prevent injection attempts from ever reaching the browser.
Is your feature request related to a problem? Please describe.
Pages and research summaries aren't templated. The header and footer are coded manually.
Describe the solution you'd like
Make a "page" template specifically for the pages and research summaries.
Describe the bug
There is a bug or typo on the Choice blog post https://blog.canada.ca/2020/09/18/expand-collapse
To Reproduce
Steps to reproduce the behavior:
details/summary
Expected behavior
Missing a T
at the beginning
Desktop (please complete the following information):
Smartphone (please complete the following information):
Is your feature request related to a problem? Please describe.
We should amplify the content design value and impact at scale for the Canada.ca blog. The blog should tell how we cultivate a design culture at Canada.ca through DesignOps.
Describe the solution you'd like
A strategic plan to define why, how and what we're doing.
Describe alternatives you've considered
A strategic canvas could do the job too.
Change “services”, to “services,” ...the comma should be inside the quote.
Describe the bug
Structured data with syntax errors detected by Google Search console
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No errors should be logged
Please add the link to the font awesome CSS to the Jekyll template.
Describe the bug
Add our site to the HSTS preload list so HSTS is active for our site in browsers by default. Our HSTS policy is only active in a browser after that browser sees a response from our site with an HSTS response header. This means new visitors will be vulnerable to exploits if they initially visit our site using an insecure HTTP URL. To eliminate this attack vector, add site to the "HSTS preload list" so browsers will apply HSTS to a site by default even before a first visit. To add our site to the list, our Strict-Transport-Security
header for all responses on all subdomains should have a max-age
setting of at least 1 year (31,536,000 seconds) and both the includeSubDomains
and preload
options should be set. The header Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
meets these requirements. Take care to get the capitalisation right for each option such as for includeSubDomains
.
To Reproduce
Preload set: None
Include subdomains: None
HSTS expiry: 31,536,000
Expected behavior
Once this is done, we can submit our site to https://hstspreload.org/ for inclusion in the HSTS preload list. Warning: As with enabling HSTS, we must be confident we won't need to disable HTTPS in the future. Removing ourself from the HSTS preload list may take some time and browsers might not keep their list up to date.
Describe the bug
The first paragraph of the section 8. Good service relies on good measurements has a coding typo
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No html tag should be visible
Describe the bug
Every page should have a title that isn't too long or too short. Well-written page titles of a suitable length will help our pages stand out in search results and help search engines understand what our pages are about. Short titles are likely lacking in enough information for both users and search engines. Long titles aren't displayed in full in search results which can be unhelpful to users.
To Reproduce
(English)
(French)
Expected behavior
Recommended page titles are between 10 and 60 characters
Describe the bug
External JavaScript should be included on pages in a way that doesn't block page rendering. A <script src="...">
tag will block HTML rendering until the JavaScript file specified is fetched and the contents of the file has finished executing. Inline JavaScript also blocks rendering until execution is complete.
To Reproduce
satelliteLib-c2082deaf69c358c641c5eb20f94b615dd606662.js
assets.adobedtm.com/caacec67651710193d2331efef325107c23a0145/satelliteLib-c2082deaf69c358c641c5eb20f94b615dd606662.js
Expected behavior
We can stop <script>
tags from blocking rendering by placing them directly before the closing </body>
tag. Alternatively, for external JavaScript files we can load the script in the background using either:
<script defer src="...">
, which delays script execution until the DOM is ready or<script async src="...">
, which will execute the script as soon as it has loaded.Note that defer scripts execute in the order they appear on the page like inline scripts. However, async scripts execute whenever they have downloaded so their execution order can change. This difference is important when scripts have dependencies.
Describe the bug
Turn off browser content sniffing to protect against content sniffing exploits. When processing a response, browsers sometimes ignore the MIME type in the Content-Type header and guess the type based on the contents of the response. This is called content sniffing and is done to improve the user experience when Content-Type headers are inaccurate or missing. However, this behaviour can be exploited. For example, if our site allows users to share images, an attacker might be able to upload a specially crafted image file that contains JavaScript code. A browser performing content sniffing might then be tricked into executing the malicious file.
To Reproduce
X-Content-Type-Options headers: None
Expected behavior
To reduce content sniffing attacks, set the X-Content-Type-Options response header to nosniff. This tells browsers to avoid guessing response types and to rely only on the Content-Type header.
I don't see this repository as one of my top repositories on my dashboard in Github. I suspect it's bc I have yet to contribute to it. Creating this issue to test whether raising an issue counts as a contribution 😁 . Will close the issue once I see what effect it has my top repos on my dashboard.
The date published and date modified section is not rendering properly at the bottom of the page.
https://deploy-preview-111--blog-tbs.netlify.app/2022/12/08/wayfinding-research-project
Describe the bug
The page-details footer file can't pick-up the date property because it's looking for a page.dateModified property
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Add a date published field that will pick-up the date property and add
Is your feature request related to a problem? Please describe.
Can we update Monday and have GitHub automatically updated or vice-versa?
Describe the solution you'd like
Describe alternatives you've considered
Describe the bug
Change title of the blog to 'Canada.ca digital design blog' in English and 'Blogue sur la conception numérique du Canada.ca'
To Reproduce
Steps to reproduce the behavior:
Describe the bug
Protect against clickjacking attacks by restricting how our pages can be embedded within iframes. Clickjacking attacks involve an attacker displaying our pages within an iframe on a site they control. For example, an attacker could overlay a UI layer over an iframe to trick visitors into triggering actions on our page as well overlaying form fields to steal data. Clickjacking has been used to exploit users into sharing links on social networks, clicking ads and stealing passwords. Protection against these attacks using the X-Frame-Options response header to restrict which hosts are allowed to embed our pages.
To Reproduce
X-Frame-Options: None
Expected behavior
The possible options are:
For example, X-Frame-Options: DENY will block all iframe usage. You should use a setting that's as restrictive as possible.
Describe the bug
Part of the title attribute can be seen on the content page
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Nothing should be there, like the English page
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Describe the bug
Some images are too wide compare to the 63-65 characters wide text surrounding them.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Would expect images sized to the text-width of surrounding text on desktop.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Is your feature request related to a problem? Please describe.
I was thinking the newsletter subscription - should be mentioned on every blog post and put something about it on the main design system page
Describe the solution you'd like
The main solution should be an email input field directly at the bottom of the blog post
Describe alternatives you've considered
If the email input field is not possible than a link to the sig-up page should do
In the blog post https://blog.canada.ca/2019/11/01/tips-travel-contact.html, go to the section called "4. Build on previous experiments and learning." Scroll down a bit to where the images are. It looks like there are 3 screencaps missing. Did they just get moved or something?
BTW, everything looks ok in the French version of the blog post.
Describe the bug
Each page should have an H1 heading that isn't excessively long to make it easier for users and search engines to understand the topic of the page. Google specifically recommends avoiding overly long headings so readers can scan your content more easily. Excessively long headings can also be an indication that paragraph text has been unhelpfully tagged as a heading.
To Reproduce
(English)
(French)
Expected behavior
Recommended H1 headings should be no longer than 60-70 characters.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.