From da9f86409dea7638743d07fc9a22b69d28543b78 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?S=C3=A9bastien=20Lorber?= Date: Thu, 23 Mar 2023 16:07:46 +0100 Subject: [PATCH] chore: fix workbox precaching page link + weird mdx structure breaking Crowdin (#8810) --- website/docs/api/plugins/plugin-pwa.mdx | 8 ++------ .../version-2.0.1/api/plugins/plugin-pwa.mdx | 8 ++------ .../version-2.1.0/api/plugins/plugin-pwa.mdx | 8 ++------ .../version-2.2.0/api/plugins/plugin-pwa.mdx | 8 ++------ .../version-2.3.1/api/plugins/plugin-pwa.mdx | 8 ++------ 5 files changed, 10 insertions(+), 30 deletions(-) diff --git a/website/docs/api/plugins/plugin-pwa.mdx b/website/docs/api/plugins/plugin-pwa.mdx index 8cb6d95fd4..2f2c8351b8 100644 --- a/website/docs/api/plugins/plugin-pwa.mdx +++ b/website/docs/api/plugins/plugin-pwa.mdx @@ -78,12 +78,8 @@ App installation requires the HTTPS protocol and a valid manifest. We enable users to browse a Docusaurus site offline, by using service-worker precaching. ->

-> -> {'What is Precaching?'} -> ->

-> +The [workbox-precaching](https://developers.google.com/web/tools/workbox/modules/workbox-precaching) page explains the idea: + > One feature of service workers is the ability to save a set of files to the cache when the service worker is installing. This is often referred to as "precaching", since you are caching content ahead of the service worker being used. > > The main reason for doing this is that it gives developers control over the cache, meaning they can determine when and how long a file is cached as well as serve it to the browser without going to the network, meaning it can be used to create web apps that work offline. diff --git a/website/versioned_docs/version-2.0.1/api/plugins/plugin-pwa.mdx b/website/versioned_docs/version-2.0.1/api/plugins/plugin-pwa.mdx index 4018a501cb..b6c2b287e1 100644 --- a/website/versioned_docs/version-2.0.1/api/plugins/plugin-pwa.mdx +++ b/website/versioned_docs/version-2.0.1/api/plugins/plugin-pwa.mdx @@ -78,12 +78,8 @@ App installation requires the HTTPS protocol and a valid manifest. We enable users to browse a Docusaurus site offline, by using service-worker precaching. ->

-> -> {'What is Precaching?'} -> ->

-> +The [workbox-precaching](https://developers.google.com/web/tools/workbox/modules/workbox-precaching) page explains the idea: + > One feature of service workers is the ability to save a set of files to the cache when the service worker is installing. This is often referred to as "precaching", since you are caching content ahead of the service worker being used. > > The main reason for doing this is that it gives developers control over the cache, meaning they can determine when and how long a file is cached as well as serve it to the browser without going to the network, meaning it can be used to create web apps that work offline. diff --git a/website/versioned_docs/version-2.1.0/api/plugins/plugin-pwa.mdx b/website/versioned_docs/version-2.1.0/api/plugins/plugin-pwa.mdx index 4018a501cb..b6c2b287e1 100644 --- a/website/versioned_docs/version-2.1.0/api/plugins/plugin-pwa.mdx +++ b/website/versioned_docs/version-2.1.0/api/plugins/plugin-pwa.mdx @@ -78,12 +78,8 @@ App installation requires the HTTPS protocol and a valid manifest. We enable users to browse a Docusaurus site offline, by using service-worker precaching. ->

-> -> {'What is Precaching?'} -> ->

-> +The [workbox-precaching](https://developers.google.com/web/tools/workbox/modules/workbox-precaching) page explains the idea: + > One feature of service workers is the ability to save a set of files to the cache when the service worker is installing. This is often referred to as "precaching", since you are caching content ahead of the service worker being used. > > The main reason for doing this is that it gives developers control over the cache, meaning they can determine when and how long a file is cached as well as serve it to the browser without going to the network, meaning it can be used to create web apps that work offline. diff --git a/website/versioned_docs/version-2.2.0/api/plugins/plugin-pwa.mdx b/website/versioned_docs/version-2.2.0/api/plugins/plugin-pwa.mdx index 4018a501cb..b6c2b287e1 100644 --- a/website/versioned_docs/version-2.2.0/api/plugins/plugin-pwa.mdx +++ b/website/versioned_docs/version-2.2.0/api/plugins/plugin-pwa.mdx @@ -78,12 +78,8 @@ App installation requires the HTTPS protocol and a valid manifest. We enable users to browse a Docusaurus site offline, by using service-worker precaching. ->

-> -> {'What is Precaching?'} -> ->

-> +The [workbox-precaching](https://developers.google.com/web/tools/workbox/modules/workbox-precaching) page explains the idea: + > One feature of service workers is the ability to save a set of files to the cache when the service worker is installing. This is often referred to as "precaching", since you are caching content ahead of the service worker being used. > > The main reason for doing this is that it gives developers control over the cache, meaning they can determine when and how long a file is cached as well as serve it to the browser without going to the network, meaning it can be used to create web apps that work offline. diff --git a/website/versioned_docs/version-2.3.1/api/plugins/plugin-pwa.mdx b/website/versioned_docs/version-2.3.1/api/plugins/plugin-pwa.mdx index 4018a501cb..b6c2b287e1 100644 --- a/website/versioned_docs/version-2.3.1/api/plugins/plugin-pwa.mdx +++ b/website/versioned_docs/version-2.3.1/api/plugins/plugin-pwa.mdx @@ -78,12 +78,8 @@ App installation requires the HTTPS protocol and a valid manifest. We enable users to browse a Docusaurus site offline, by using service-worker precaching. ->

-> -> {'What is Precaching?'} -> ->

-> +The [workbox-precaching](https://developers.google.com/web/tools/workbox/modules/workbox-precaching) page explains the idea: + > One feature of service workers is the ability to save a set of files to the cache when the service worker is installing. This is often referred to as "precaching", since you are caching content ahead of the service worker being used. > > The main reason for doing this is that it gives developers control over the cache, meaning they can determine when and how long a file is cached as well as serve it to the browser without going to the network, meaning it can be used to create web apps that work offline.