From a06798b25258416538dcd7035fe9e4432b6493fb Mon Sep 17 00:00:00 2001 From: Hung Viet Nguyen Date: Thu, 4 Feb 2021 18:58:30 +0700 Subject: [PATCH 01/38] docs: Make hyperlink consistent --- docusaurus/docs/pre-rendering-into-static-html-files.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docusaurus/docs/pre-rendering-into-static-html-files.md b/docusaurus/docs/pre-rendering-into-static-html-files.md index f9bab58190e..5551745f648 100644 --- a/docusaurus/docs/pre-rendering-into-static-html-files.md +++ b/docusaurus/docs/pre-rendering-into-static-html-files.md @@ -4,7 +4,7 @@ title: Pre-Rendering into Static HTML Files sidebar_label: Pre-Rendering Static HTML --- -If you’re hosting your `build` with a static hosting provider you can use [react-snapshot](https://www.npmjs.com/package/react-snapshot) or [react-snap](https://github.com/stereobooster/react-snap) to generate HTML pages for each route, or relative link, in your application. These pages will then seamlessly become active, or “hydrated”, when the JavaScript bundle has loaded. +If you’re hosting your `build` with a static hosting provider you can use [react-snapshot](https://www.npmjs.com/package/react-snapshot) or [react-snap](https://www.npmjs.com/package/react-snap) to generate HTML pages for each route, or relative link, in your application. These pages will then seamlessly become active, or “hydrated”, when the JavaScript bundle has loaded. There are also opportunities to use this outside of static hosting, to take the pressure off the server when generating and caching routes. From b7b0d776d19be3370cdb3b3e73df6a132991cf67 Mon Sep 17 00:00:00 2001 From: imdkbj <46839821+imdkbj@users.noreply.github.com> Date: Fri, 12 Feb 2021 13:29:36 +0530 Subject: [PATCH 02/38] Updated pace.js link --- docusaurus/docs/using-the-public-folder.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docusaurus/docs/using-the-public-folder.md b/docusaurus/docs/using-the-public-folder.md index 71266db6f81..a33c3a29ec8 100644 --- a/docusaurus/docs/using-the-public-folder.md +++ b/docusaurus/docs/using-the-public-folder.md @@ -60,7 +60,7 @@ The `public` folder is useful as a workaround for a number of less common cases: - You need a file with a specific name in the build output, such as [`manifest.webmanifest`](https://developer.mozilla.org/en-US/docs/Web/Manifest). - You have thousands of images and need to dynamically reference their paths. -- You want to include a small script like [`pace.js`](https://github.hubspot.com/pace/docs/welcome/) outside of the bundled code. +- You want to include a small script like [`pace.js`](https://github.com/CodeByZach/pace) outside of the bundled code. - Some libraries may be incompatible with webpack and you have no other option but to include it as a `