Redundancy-free internal links (GoogleChrome#5104)

* Remove redundant https://web.dev prefixes in links

* Fix two files

Author: tomayac

CONTRIBUTING.md

@@ -12,18 +12,18 @@ proposal.
 
 ### Contributor License Agreements
 
-We'd love to accept your code patches! However, before we can take them, we 
+We'd love to accept your code patches! However, before we can take them, we
 have to jump a couple of legal hurdles.
 
-Please fill out either the individual or corporate Contributor License 
+Please fill out either the individual or corporate Contributor License
 Agreement.
 
-* If you are an individual writing original source code and you're sure you 
+* If you are an individual writing original source code and you're sure you
 own the intellectual property, then sign an [individual CLA](https://developers.google.com/open-source/cla/individual).
-* If you work for a company that wants to allow you to contribute your work, 
+* If you work for a company that wants to allow you to contribute your work,
 then sign a [corporate CLA](https://developers.google.com/open-source/cla/corporate).
 
-Follow either of the two links above to access the appropriate CLA and 
+Follow either of the two links above to access the appropriate CLA and
 instructions for how to sign and return it.
 
 1. Sign the contributors license agreement above.
@@ -39,7 +39,7 @@ the CLA.
 
 ## Writing Code
 
-If your contribution contains code, please make sure that it follows 
+If your contribution contains code, please make sure that it follows
 [the style guide](https://google.github.io/styleguide/jsguide.html).
 Otherwise, we will have to ask you to make changes, and that's no fun for anyone.
 

src/site/content/en/blog/a11y-tips-for-web-dev/index.md

@@ -464,7 +464,7 @@ debugging the accessibility of your visual components.
   Tenon has strong integration support across build tools, browsers (via extensions), and even text editors.
 - There are many library- and framework-specific tools
   for highlighting accessibility issues with components.
-  For example, [web.dev](https://web.dev/accessibility-auditing-react/)
+  For example, [web.dev](/accessibility-auditing-react/)
   explains how to use [eslint-plugin-jsx-a11y](https://www.npmjs.com/package/eslint-plugin-jsx-a11y)
   to highlight accessibility issues for React components in your editor:
 

src/site/content/en/blog/agrofy/index.md

@@ -20,10 +20,10 @@ America's agribusiness market. They match up buyers and sellers of farm
 machines, land, equipment, and financial services. In Q3 2020 a 4-person
 development team at Agrofy spent a month optimizing their website because they
 hypothesized that improved performance would lead to reduced bounce rates. They
-specifically focused on improving [LCP](https://web.dev/lcp/), which is one of
-the [Core Web Vitals](https://web.dev/vitals/#core-web-vitals). These
+specifically focused on improving [LCP](/lcp/), which is one of
+the [Core Web Vitals](/vitals/#core-web-vitals). These
 performance optimizations led to a 70% improvement in LCP, which correlated to a
-76% reduction in load abandonment (from 3.8% to 0.9%).  
+76% reduction in load abandonment (from 3.8% to 0.9%).
 
 <div class="w-stats">
   <div class="w-stat">
@@ -38,8 +38,8 @@ performance optimizations led to a 70% improvement in LCP, which correlated to a
 
 ## Problem
 
-While studying their business metrics, a development team at Agrofy noticed 
-that their bounce rates seemed higher than industry benchmarks. Technical 
+While studying their business metrics, a development team at Agrofy noticed
+that their bounce rates seemed higher than industry benchmarks. Technical
 debt was also increasing in the website codebase.
 
 ## Solution
@@ -52,30 +52,30 @@ The Agrofy team pitched their executives and got buy-in to:
 
 The migration took 2 months. Aside from the 4-person development team mentioned
 earlier, this migration also involved product and UX specialists and a software
-architect.  
+architect.
 The optimization project took the 4-person development team 1 month. They
-focused on LCP, [CLS](https://web.dev/cls/) (another Core Web Vitals metric),
-and [FCP](https://web.dev/fcp/). Specific optimizations included:
+focused on LCP, [CLS](/cls/) (another Core Web Vitals metric),
+and [FCP](/fcp/). Specific optimizations included:
 
 +   Lazy loading all non-visible elements with the
     [Intersection Observer API](https://developer.mozilla.org/en-US/docs/Web/API/Intersection_Observer_API).
 +   Delivering static resources faster with a [content delivery
-    network](https://web.dev/content-delivery-networks/).
-+   [Lazy loading images](https://web.dev/browser-level-image-lazy-loading/)
+    network](/content-delivery-networks/).
++   [Lazy loading images](/browser-level-image-lazy-loading/)
     with `loading="lazy"`.
 +   [Server-side rendering](https://developers.google.com/web/updates/2019/02/rendering-on-the-web)
     of
     [critical rendering path](https://developers.google.com/web/fundamentals/performance/critical-rendering-path)
     content.
-+   [Preloading and preconnecting](https://web.dev/fast/#optimize-your-resource-delivery)
++   [Preloading and preconnecting](/fast/#optimize-your-resource-delivery)
     critical resources to minimize handshake times.
 +   Using real user monitoring (RUM) tools to identify which product detail
     pages were experiencing lots of layout shifts and then make adjustments to
     the codebase's architecture.
 
 Check out the
 [Agrofy engineering blog post](https://mollar-luciano.medium.com/how-agrofy-optimised-core-web-vitals-and-improved-business-metrics-2f73311bca)
-for more technical details.  
+for more technical details.
 
 After enabling the new codebase on 20% of traffic, they launched the new site to
 all visitors in early September 2020.
@@ -88,11 +88,11 @@ different metrics:
 +   LCP improved 70%.
 +   CLS improved 72%.
 +   Blocking JS requests reduced 100% and blocking CSS requests 80%.
-+   [Long tasks](https://web.dev/long-tasks-devtools/) reduced 72%.
-+   [First CPU Idle](https://web.dev/first-cpu-idle/) improved 25%.
++   [Long tasks](/long-tasks-devtools/) reduced 72%.
++   [First CPU Idle](/first-cpu-idle/) improved 25%.
 
 Over the same time frame, real user monitoring data (also known as [field
-data](https://web.dev/how-to-measure-speed/#lab-data-vs-field-data)) showed that
+data](/how-to-measure-speed/#lab-data-vs-field-data)) showed that
 the load abandonment rate on product detail pages dropped 76%, from 3.8% to
 0.9%:
 

src/site/content/en/blog/app-shortcuts/index.md

@@ -238,7 +238,7 @@ Check out the [app shortcuts sample] and its [source].
 * Blink Component: [`UI>Browser>WebAppInstalls`]
 
 [Progressive Web Apps]: /progressive-web-apps/
-[What does it take to be installable?]: https://web.dev/install-criteria/
+[What does it take to be installable?]: /install-criteria/
 [scope]: /add-manifest/#scope
 [web app manifest]: /add-manifest
 [web app manifest icons]: /add-manifest/#icons

src/site/content/en/blog/ar-hit-test/index.md

@@ -33,9 +33,9 @@ In this article I assume you already know how to create an augmented reality
 session and that you know how to run a frame loop. If you're not familiar with
 these concepts, you should read the earlier articles in this series.
 
-* [Virtual reality comes to the web](https://web.dev/vr-comes-to-the-web/)
-* [Virtual reality comes to the web, part II](https://web.dev/vr-comes-to-the-web-pt-ii/)
-* [Web AR: you may already know how to use it](https://web.dev/web-ar)
+* [Virtual reality comes to the web](/vr-comes-to-the-web/)
+* [Virtual reality comes to the web, part II](/vr-comes-to-the-web-pt-ii/)
+* [Web AR: you may already know how to use it](/web-ar)
 
 ## The immersive AR session sample
 

src/site/content/en/blog/aspect-ratio/index.md

@@ -16,7 +16,7 @@ tags:
 {% Aside %}
 
 Summary: Maintaining a consistent width-to-height ratio, called an *aspect ratio*, is critical in
-responsive web design and for preventing [cumulative layout shift](https://web.dev/cls/). Now,
+responsive web design and for preventing [cumulative layout shift](/cls/). Now,
 there's a more straightforward way to do this with the new `aspect-ratio` property launching in
 [Chromium 88](https://www.chromestatus.com/feature/5738050678161408), [Firefox
 87](https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Experimental_features#property_aspect-ratio), and [Safari Technology Preview
@@ -241,7 +241,7 @@ img {
 
 ### Bonus tip: image attributes for aspect ratio
 
-Another way to set an image's aspect ratio is through [image attributes](https://www.smashingmagazine.com/2020/03/setting-height-width-images-important-again/). If you know the dimensions of the image ahead of time, it is a [best practice](https://web.dev/image-aspect-ratio/#check-the-image's-width-and-height-attributes-in-the-html) to
+Another way to set an image's aspect ratio is through [image attributes](https://www.smashingmagazine.com/2020/03/setting-height-width-images-important-again/). If you know the dimensions of the image ahead of time, it is a [best practice](/image-aspect-ratio/#check-the-image's-width-and-height-attributes-in-the-html) to
 set these dimensions as its `width` and `height`.
 
 For our example above, knowing the dimensions are 800px by 600px, the image markup would look like: `<img src="image.jpg"

src/site/content/en/blog/async-clipboard/index.md

@@ -402,7 +402,7 @@ simplified events aligned with the
 [Drag and Drop API](https://developer.mozilla.org/en-US/docs/Web/API/HTML_Drag_and_Drop_API).
 Because of potential risks Chrome is
 treading carefully. To stay up to date on Chrome's progress, watch this article
-and our [blog](https://web.dev/blog/) for updates.
+and our [blog](/blog/) for updates.
 
 For now, support for the Clipboard API is available in
 [a number of browsers](https://developer.mozilla.org/en-US/docs/Web/API/Clipboard#Browser_compatibility).

src/site/content/en/blog/at-property/index.md

@@ -129,8 +129,8 @@ each gradient declaration is parsed as a string.
 <figure class="w-figure">
   <img class="w-screenshot" src="https://storage.googleapis.com/web-dev-assets/at-property/support1.gif">
   <figcaption class="w-figcaption">
-    Using a custom property with a "number" syntax, the gradient on the left shows a smooth 
-    transition between stop values. The gradient on the right uses a default custom property 
+    Using a custom property with a "number" syntax, the gradient on the left shows a smooth
+    transition between stop values. The gradient on the right uses a default custom property
     (no syntax defined) and shows an abrupt transition.
   </figcaption>
 </figure>
@@ -140,8 +140,8 @@ each gradient declaration is parsed as a string.
     <source src="https://storage.googleapis.com/web-dev-assets/at-property/support1.mp4" type="video/mp4">
   </video>
   <figcaption class="w-figcaption">
-    Using a custom property with a "number" syntax, the gradient on the left shows a smooth 
-    transition between stop values. The gradient on the right uses a default custom property 
+    Using a custom property with a "number" syntax, the gradient on the left shows a smooth
+    transition between stop values. The gradient on the right uses a default custom property
     (no syntax defined) and shows an abrupt transition.
   </figcaption>
 </figure>
@@ -231,7 +231,7 @@ you could write something like:
 }
 ```
 
-## Conclusion 
+## Conclusion
 
 The `@property` rule makes an exciting technology even more accessible by
 allowing you to write semantically meaningful CSS within CSS itself. To learn
@@ -240,7 +240,7 @@ resources:
 
 - [Is Houdini Ready Yet?](http://ishoudinireadyyet.com/)
 - [MDN Houdini Reference](https://developer.mozilla.org/en-US/docs/Web/Houdini)
-- [Smarter custom properties with Houdini's new API](https://web.dev/css-props-and-vals/)
+- [Smarter custom properties with Houdini's new API](/css-props-and-vals/)
 - [Houdini CSSWG Issue Queue](https://github.com/w3c/css-houdini-drafts/issues)
 
 Photo by [Cristian Escobar](https://unsplash.com/@cristian1) on Unsplash.

src/site/content/en/blog/autowebperf/index.md

@@ -23,14 +23,14 @@ tags:
 [AutoWebPerf](https://github.com/GoogleChromeLabs/AutoWebPerf) (AWP) is a
 modular tool that enables automatic gathering of performance data from multiple
 sources. Currently there are [many tools
-available](https://web.dev/vitals-tools/) to measure website performance for
+available](/vitals-tools/) to measure website performance for
 different scopes ([lab and
-field](https://web.dev/how-to-measure-speed/#lab-data-vs-field-data)), such as
+field](/how-to-measure-speed/#lab-data-vs-field-data)), such as
 Chrome UX Report, PageSpeed Insights, or WebPageTest. AWP offers integration
 with various audit tools with a simple setup so you can continuously monitor the
 site performance in one place.
 
-The release of [Web Vitals](https://web.dev/vitals/) guidance means that close
+The release of [Web Vitals](/vitals/) guidance means that close
 and active monitoring of web pages is becoming increasingly important. The
 engineers behind this tool have been doing performance audits for years and they
 created AWP to automate a manual, recurring, and time consuming part of their
@@ -47,14 +47,14 @@ Although several tools and APIs are available to monitor the performance of web
 pages, most of them expose data measured at a specific time. To adequately
 monitor a website and maintain good performance of key pages, it's recommended
 to continuously take measurements of [Core Web
-Vitals](https://web.dev/vitals/#core-web-vitals) over time and observe trends.
+Vitals](/vitals/#core-web-vitals) over time and observe trends.
 
 AWP makes that easier by providing an engine and pre-built API integrations
 which can be programmatically configured to automate recurrent queries to
 various performance monitoring APIs.
 
 For example, with AWP, you can set a daily test on your home page to capture the
-field data from [CrUX API](https://web.dev/chrome-ux-report-api/) and lab data
+field data from [CrUX API](/chrome-ux-report-api/) and lab data
 from a
 [Lighthouse report from PageSpeed Insights](https://developers.google.com/speed/pagespeed/insights/).
 This data can be written and stored over time, for example, in [Google
@@ -82,8 +82,8 @@ Google Sheets).
 AWP comes with a number of pre-implemented gatherers and connectors:
 
 * Pre-implemented gatherers:
-  * [CrUX API](https://web.dev/chrome-ux-report-api/)
-  * [CrUX BigQuery](https://web.dev/chrome-ux-report-bigquery/)
+  * [CrUX API](/chrome-ux-report-api/)
+  * [CrUX BigQuery](/chrome-ux-report-bigquery/)
   * [PageSpeed Insights API](https://developers.google.com/speed/docs/insights/v5/get-started)
   * [WebPageTest API](https://www.webpagetest.org/getkey.php)
 * Pre-implemented connectors:

src/site/content/en/blog/betty-crocker/index.md

@@ -61,7 +61,7 @@ Betty Crocker asked themselves how they could port the killer feature of their i
 over to the web app.
 This is when they learned about
 [Project Fugu](https://developers.google.com/web/updates/capabilities) and the
-[Wake Lock API](https://web.dev/wakelock/).
+[Wake Lock API](/wakelock/).
 
 {% Img src="image/admin/Yoj65m20XpoPdaL8ejAv.jpg", alt="A person kneading dough on a kitchen table covered in flour", width="800", height="533" %}
 
@@ -346,7 +346,7 @@ Other examples are boarding pass or ticket apps that need to keep the screen on
 until the barcode has been scanned, kiosk-style apps that keep the screen on continuously,
 or web-based presentation apps that prevent the screen from sleeping during a presentation.
 
-We have compiled [everything you need to know about the Wake Lock API](https://web.dev/wakelock/)
+We have compiled [everything you need to know about the Wake Lock API](/wakelock/)
 in a comprehensive article on this very site.
 Happy reading, and happy cooking!
 

src/site/content/en/blog/bfcache/index.md

@@ -55,7 +55,7 @@ loads:
       <td>
         A new request is initiated to load the previous page, and, depending
         on how well that page has been <a
-        href="https://web.dev/reliable/#the-options-in-your-caching-toolbox">
+        href="/reliable/#the-options-in-your-caching-toolbox">
         optimized</a> for repeat visits, the browser might have to re-download,
         re-parse, and re-execute some (or all) of resources it just downloaded.
       </td>

src/site/content/en/blog/browser-fs-access/index.md

@@ -251,7 +251,7 @@ the demo cannot be embedded in this article.
 ## The browser-fs-access library in the wild
 
 In my free time, I contribute a tiny bit to an
-[installable PWA](https://web.dev/progressive-web-apps/#installable)
+[installable PWA](/progressive-web-apps/#installable)
 called [Excalidraw](https://excalidraw.com/),
 a whiteboard tool that lets you easily sketch diagrams with a hand-drawn feel.
 It is fully responsive and works well on a range of devices from small mobile phones to computers with large screens.

src/site/content/en/blog/building-a-pwa-at-google-part-1/index.md

@@ -29,9 +29,9 @@ means a complete overview of PWAs. The aim is to share learnings from our team's
 For this first post we'll cover a little background information first and then dive into all the
 stuff we learned about service workers.
 
-{% Aside %}  
+{% Aside %}
 Bulletin was shut down in 2019 due to lack of product/market fit. We still learned a lot about PWAs
-along the way!  
+along the way!
 {% endAside %}
 
 ## Background {: #background }
@@ -44,7 +44,7 @@ Before we delve into the development process, let's examine why building a PWA w
 option for this project:
 
 * **Ability to iterate quickly**. Especially valuable since Bulletin would be piloted in
-  multiple markets. 
+  multiple markets.
 * **Single code base**. Our users were roughly evenly split between Android and iOS. A PWA meant
   we could build a single web app that would work on both platforms. This increased the velocity
   and impact of the team.
@@ -66,7 +66,7 @@ You can't have a PWA without a [service
 worker](https://developers.google.com/web/fundamentals/primers/service-workers/). Service workers
 give you a lot of power, such as advanced caching strategies, offline capabilities, background sync,
 etc. While service workers do add some complexity, we found that their benefits outweighed the added
-complexity. 
+complexity.
 
 ### Generate it if you can {: #generate }
 
@@ -142,13 +142,13 @@ disable the memory cache. In order to cover more browsers, we opted for a differ
 including a flag to disable caching in our service worker which is enabled by default on developer
 builds. This ensures that devs always get their most recent changes without any caching issues. It's
 important to include the `Cache-Control: no-cache` header as well to [prevent the browser from
-caching any assets](https://web.dev/http-cache/#unversioned-urls).
+caching any assets](/http-cache/#unversioned-urls).
 
 ### Lighthouse {: #lighthouse }
 
 [Lighthouse](https://developers.google.com/web/tools/lighthouse/) provides a number of debugging
 tools useful for PWAs. It scans a site and generates reports covering PWAs, performance,
-accessibility, SEO, and other best practices.  
+accessibility, SEO, and other best practices.
 We recommend [running Lighthouse on continuous
 integration](https://github.com/GoogleChrome/lighthouse-ci) to alert you if you break one of the
 criteria to be a PWA. This actually happened to us once, where the service worker wasn't installing

src/site/content/en/blog/building-a-settings-component/index.md

@@ -194,8 +194,8 @@ want a large gap, but not as large as if we're on a wide screen.
 
 The `grid-template-columns` property uses 3 CSS functions: `repeat()`, `minmax()` and
 `min()`. [Una Kravets](#) has a [great layout blog
-post](https://web.dev/one-line-layouts/) about this, calling it
-[RAM](https://web.dev/one-line-layouts/#07.-ram-(repeat-auto-minmax):-grid-template-columns(auto-fit-minmax(lessbasegreater-1fr))).
+post](/one-line-layouts/) about this, calling it
+[RAM](/one-line-layouts/#07.-ram-(repeat-auto-minmax):-grid-template-columns(auto-fit-minmax(lessbasegreater-1fr))).
 
 There's 3 special additions in our layout, if you compare it to Una's:
 
@@ -433,8 +433,8 @@ a better location:
 ```
 
 Learn all about it in this [`color-scheme`
-article](https://web.dev/color-scheme/) by [Thomas
-Steiner](https://web.dev/authors/thomassteiner/). There's a lot more to gain
+article](/color-scheme/) by [Thomas
+Steiner](/authors/thomassteiner/). There's a lot more to gain
 than dark checkbox inputs!
 
 ### CSS `accent-color`
@@ -677,7 +677,7 @@ is a Level 5 spec addition that
 
 The goal was an easy to manage and animated visual highlight for user feedback.
 By using a box shadow I can avoid [triggering
-layout](https://web.dev/animations-guide/#triggers) with the effect. I do this
+layout](/animations-guide/#triggers) with the effect. I do this
 by creating a shadow that's not blurred and matches the circular shape of the
 thumb element. Then I change and transition it's spread size on hover.