Removes and redirects Lighthouse landing page (#9601)

* Removes and redirects Lighthouse overview, updates some links. * Fixes tests yelling. * Fixes even more test yelling.

Author: malchata

src/content/en/_index.yaml

@@ -31,8 +31,8 @@ landing_page:
  <h3>Tools</h3>
  <p>
  <a href="/web/tools/chrome-devtools/" class="gc-analytics-event" data-category="webFu" data-label="devtools-landing" data-action="web-home">Chrome DevTools</a>,
- <a href="/web/tools/lighthouse/" class="gc-analytics-event" data-category="webFu" data-label="lighthouse-landing" data-action="web-home">Lighthouse</a>,
- <a href="/web/tools/workbox/" class="gc-analytics-event" data-category="webFu" data-label="workbox-landing" data-action="web-home">Workbox</a>,
+ <a href="https://developer.chrome.com/docs/lighthouse/overview/" class="gc-analytics-event" data-category="webFu" data-label="lighthouse-landing" data-action="web-home">Lighthouse</a>,
+ <a href="https://developer.chrome.com/docs/workbox/" class="gc-analytics-event" data-category="webFu" data-label="workbox-landing" data-action="web-home">Workbox</a>,
  and more tools to make your life easier and improve your
  development artistry.
  </p>

src/content/en/_redirects.yaml

@@ -130,6 +130,9 @@ redirects:
 - from: /web/fundamentals/discovery/search-optimization
  to: https://web.dev/lighthouse-seo/
 
+- from: /web/tools/lighthouse/
+ to: https://developer.chrome.com/docs/lighthouse/overview/
+
 - from: /web/fundamentals/engage-and-retain/app-install-banners/...
  to: https://web.dev/customize-install/
 

src/content/en/showcase/2017/voot.md

@@ -2,7 +2,7 @@ project_path: /web/_project.yaml
 book_path: /web/showcase/_book.yaml
 
 {# wf_published_on: 2017-04-20 #}
-{# wf_updated_on: 2018-03-20 #}
+{# wf_updated_on: 2022-06-01 #}
 {# wf_featured_image: /web/showcase/2017/images/voot/voot-lite.png #}
 {# wf_featured_snippet: Voot.com launches their media Progressive Web App in India. Within days of implementation, session time per user increased by 39% and daily views per user by 15%. #}
 {# wf_tags: media,casestudy #}
@@ -66,7 +66,7 @@ capabilities.
 
 Voot.com also decreased load times by adding a service worker to preload images
 as the user navigates, and to cache images for repeat visits. The site was also
-analyzed with [Lighthouse](/web/tools/lighthouse/) to gain performance insights,
+analyzed with [Lighthouse](https://developer.chrome.com/docs/lighthouse/overview/) to gain performance insights,
 which in turn allowed a reduction in JavaScript and CSS overhead and the
 implementation of synchronous server calls.
 

src/content/en/showcase/2018/nikkei.md

@@ -2,7 +2,7 @@ project_path: /web/_project.yaml
 book_path: /web/showcase/_book.yaml
 
 {# wf_published_on: 2018-11-19 #}
-{# wf_updated_on: 2018-11-19 #}
+{# wf_updated_on: 2022-06-01 #}
 {# wf_blink_components: N/A #}
 {# wf_featured_image: /web/showcase/2018/images/nikkei/featured.jpg #}
 {# wf_featured_snippet: With a publishing history of more than 140 years, Nikkei is one of the most authoritative media businesses in Japan. To provide a better user experience and accelerate their business on the web, Nikkei successfully launched a Progressive Web App in November 2017, and they’re seeing amazing results from the new platform. #}
@@ -84,7 +84,7 @@ results from the new platform.
 
 Nikkei saw a rapid rise in mobile traffic to their legacy website as
 smartphones became the main point of entry to the web for many users.
-However, using [Lighthouse](/web/tools/lighthouse/), an auditing tool that
+However, using [Lighthouse](https://developer.chrome.com/docs/lighthouse/overview/), an auditing tool that
 scans a web page and gives recommendations on how to improve across multiple
 categories, they understood that their site wasn’t fully optimized for mobile
 across multiple areas and was very slow to load.
@@ -160,7 +160,7 @@ performance was entirely within their control, they optimized their
 
 Speed is more important than ever. As smartphones became the main browsing
 device for many users, Nikkei saw a rapid increase of mobile traffic on
-their service. But using [Lighthouse](/web/tools/lighthouse/), they realized
+their service. But using [Lighthouse](https://developer.chrome.com/docs/lighthouse/overview/), they realized
 that their legacy website wasn’t fully optimized for mobile, with the Speed
 Index averaging 10 seconds, very slow initial load, and a large JavaScript
 bundle. It was time for Nikkei to rebuild their website and adapt

src/content/en/shows/http203/podcast/io-chats-ewa.md

@@ -2,7 +2,7 @@ project_path: /web/_project.yaml
 book_path: /web/shows/_book.yaml
 description: Getting performance right.
 
-{# wf_updated_on: 2018-06-29 #}
+{# wf_updated_on: 2022-06-01 #}
 {# wf_published_on: 2018-06-19 #}
 {# wf_podcast_audio: https://storage.googleapis.com/http-203-podcast/io-2018-ewa.mp3 #}
 {# wf_podcast_duration: 00:15:46 #}
@@ -19,7 +19,7 @@ In this episode we chat to [Ewa Gasperowicz](https://twitter.com/devnook), anoth
 Chrome dev-rels. We cover:
 
 * Getting web performance right.
-* Getting performance tests into [Lighthouse](/web/tools/lighthouse/).
+* Getting performance tests into [Lighthouse](https://developer.chrome.com/docs/lighthouse/overview/).
 * Does a "functionality first" approach mean performance is forgotten about?
 * How it's no longer possible to know all browser technologies.
 

src/content/en/shows/http203/podcast/io-chats-v-eric.md

@@ -2,7 +2,7 @@ project_path: /web/_project.yaml
 book_path: /web/shows/_book.yaml
 description: Lighthouse and automation.
 
-{# wf_updated_on: 2018-08-02 #}
+{# wf_updated_on: 2022-06-01 #}
 {# wf_published_on: 2018-08-02 #}
 {# wf_podcast_audio: https://storage.googleapis.com/http-203-podcast/io-2018-v-eric.mp3 #}
 {# wf_podcast_duration: 00:18:17 #}
@@ -19,7 +19,7 @@ In this episode we chat to [Vinamrata Singal](https://twitter.com/vinamratas), w
 Lighthoue, and [Eric Bidelman](https://twitter.com/ebidel) who is someone else we know. We cover
 stuff like:
 
-* [Lighthouse](/web/tools/lighthouse/).
+* [Lighthouse](https://developer.chrome.com/docs/lighthouse/overview/).
 * [Headless Chrome](/web/updates/2017/04/headless-chrome).
 * [Puppeteer](/web/tools/puppeteer/).
 * Chrome's [DevTools protocol](https://chromedevtools.github.io/devtools-protocol/).

src/content/en/tools/_book.yaml

@@ -24,7 +24,8 @@ upper_tabs:
  - name: Workbox
  contents:
  - title: Workbox
- path: /web/tools/workbox
+ path: https://developer.chrome.com/docs/workbox/
+ status: external
  - name: Chrome User Experience Report
  contents:
  - title: Chrome User Experience Report

src/content/en/tools/_index.yaml

@@ -28,10 +28,10 @@ landing_page:
  Audits panel. You can also run Lighthouse from the command line or
  install the Chrome Extension.
  image_path: images/lighthouse-16x9.png
- path: /web/tools/lighthouse/
+ path: https://developer.chrome.com/docs/lighthouse/overview/
  buttons:
  - label: Get started
- path: /web/tools/lighthouse/
+ path: https://developer.chrome.com/docs/lighthouse/overview/
  - heading: Puppeteer
  description: >
  Puppeteer is a Node library which provides a high-level API to control
@@ -48,10 +48,12 @@ landing_page:
  easy to build an offline PWA and take advantage of the service worker
  APIs.
  image_path: images/workbox-16x9.png
- path: /web/tools/workbox/
+ path: https://developer.chrome.com/docs/workbox/
+ status: external
  buttons:
  - label: Get started
- path: /web/tools/workbox/
+ path: https://developer.chrome.com/docs/workbox/
+ status: external
 
  - classname: devsite-landing-row-cards
  items:

src/content/en/tools/_menu_toc.yaml

@@ -4,7 +4,8 @@ included:
  - label: Chrome DevTools
  path: https://developer.chrome.com/docs/devtools/
  - label: Lighthouse
- path: /web/tools/lighthouse
+ path: https://developer.chrome.com/docs/lighthouse/overview/
+ status: external
  - label: Puppeteer
  path: /web/tools/puppeteer
  - label: Workbox

src/content/en/tools/_redirects.yaml

@@ -122,6 +122,9 @@ redirects:
 
 # Lighthouse
 
+- from: /web/tools/lighthouse/run
+ to: https://web.dev/measure/
+
 - from: /web/tools/lighthouse/audits/critical-request-chains
  to: https://web.dev/critical-request-chains/