diff --git a/docs/en/1.0.11/commands.html b/docs/en/1.0.11/commands.html index 9ed235c8be..9fda92c3a1 100644 --- a/docs/en/1.0.11/commands.html +++ b/docs/en/1.0.11/commands.html @@ -83,19 +83,19 @@

Running from the command line

The scripts can be run using either Yarn or npm. If you've already gone through our Getting Started guide, you may already be familiar with the start command. It's the command that tells Docusaurus to run the docusaurus-start script which generates the site and starts up a server, and it's usually invoked like so:

-
yarn run start
-
+
yarn run start
+

The same script can be invoked using npm:

-
npm run start
-
+
npm run start
+

To run a particular script, just replace the start command in the examples above with the command associated with your script.

Using arguments

Some commands support optional arguments. For example, to start a server on port 8080, you can specify the --port argument when running start:

-
yarn run start --port 8080
-
+
yarn run start --port 8080
+

If you run Docusaurus using npm, you can still use the command line arguments by inserting a -- between npm run <command> and the command arguments:

-
npm run start -- --port 8080
-
+
npm run start -- --port 8080
+

Configuration

These scripts are set up under the "scripts" key in your website/package.json file as part of the installation process. If you need help setting them up again, please refer to the Installation guide.

Docusaurus provides some default mappings to allow you to run commands following Node conventions. Instead of typing docusaurus-start every time, you can type yarn run start or npm start to achieve the same.

diff --git a/docs/en/1.0.11/commands/index.html b/docs/en/1.0.11/commands/index.html index 9ed235c8be..9fda92c3a1 100644 --- a/docs/en/1.0.11/commands/index.html +++ b/docs/en/1.0.11/commands/index.html @@ -83,19 +83,19 @@

Running from the command line

The scripts can be run using either Yarn or npm. If you've already gone through our Getting Started guide, you may already be familiar with the start command. It's the command that tells Docusaurus to run the docusaurus-start script which generates the site and starts up a server, and it's usually invoked like so:

-
yarn run start
-
+
yarn run start
+

The same script can be invoked using npm:

-
npm run start
-
+
npm run start
+

To run a particular script, just replace the start command in the examples above with the command associated with your script.

Using arguments

Some commands support optional arguments. For example, to start a server on port 8080, you can specify the --port argument when running start:

-
yarn run start --port 8080
-
+
yarn run start --port 8080
+

If you run Docusaurus using npm, you can still use the command line arguments by inserting a -- between npm run <command> and the command arguments:

-
npm run start -- --port 8080
-
+
npm run start -- --port 8080
+

Configuration

These scripts are set up under the "scripts" key in your website/package.json file as part of the installation process. If you need help setting them up again, please refer to the Installation guide.

Docusaurus provides some default mappings to allow you to run commands following Node conventions. Instead of typing docusaurus-start every time, you can type yarn run start or npm start to achieve the same.

diff --git a/docs/en/1.0.11/navigation.html b/docs/en/1.0.11/navigation.html index 98cc40bc29..44cfc3c68c 100644 --- a/docs/en/1.0.11/navigation.html +++ b/docs/en/1.0.11/navigation.html @@ -138,28 +138,28 @@

To expose sidebars, you will add clickable labels to the site navigation bar at the top of the website. You can add documents, pages and external links.

Adding Documents

After creating a new sidebar for the site by adding it to sidebars.json, you can expose the new sidebar from the top navigation bar by editing the headerLinks field of siteConfig.js.

-
headerLinks: [
+
headerLinks: [
+  ...
+  { doc: 'my-examples', label: 'Examples' },
   ...
-  { doc: 'my-examples', label: 'Examples' },
-  ...
 ],
 

 
A label called Examples will be added to the site navigation bar and when you click on it at the top of your site, the examples-sidebar will be shown and the default document will be my-examples.

 
Adding Custom Pages

 
To add custom pages to the site navigation bar, entries can be added to the headerLinks of siteConfig.js. For example, if we have a page within website/pages/help.js, we can link to it by adding the following:

-
headerLinks: [
+
headerLinks: [
+  ...
+  { page: 'help', label: 'Help' },
   ...
-  { page: 'help', label: 'Help' },
-  ...
 ],
 

 
A label called Help will be added to the site navigation bar and when you click on it at the top of your site, the content from the help.js page will be shown.

 
Adding External Links

 
Custom links can be added to the site navigation bar with the following entry in siteConfig.js:

-
headerLinks: [
+
headerLinks: [
+  ...
+  { href: 'https://github.com/facebook/Docusaurus', label: 'GitHub' },
   ...
-  { href: 'https://github.com/facebook/Docusaurus', label: 'GitHub' },
-  ...
 ],
 

 
A label called GitHub will be added to the site navigation bar and when you click on it at the top of your site, the content of the external link will be shown.

diff --git a/docs/en/1.0.11/navigation/index.html b/docs/en/1.0.11/navigation/index.html
index 98cc40bc29..44cfc3c68c 100644
--- a/docs/en/1.0.11/navigation/index.html
+++ b/docs/en/1.0.11/navigation/index.html
@@ -138,28 +138,28 @@
 
To expose sidebars, you will add clickable labels to the site navigation bar at the top of the website. You can add documents, pages and external links.

 
Adding Documents

 
After creating a new sidebar for the site by adding it to sidebars.json, you can expose the new sidebar from the top navigation bar by editing the headerLinks field of siteConfig.js.

-
headerLinks: [
+
headerLinks: [
+  ...
+  { doc: 'my-examples', label: 'Examples' },
   ...
-  { doc: 'my-examples', label: 'Examples' },
-  ...
 ],
 

 
A label called Examples will be added to the site navigation bar and when you click on it at the top of your site, the examples-sidebar will be shown and the default document will be my-examples.

 
Adding Custom Pages

 
To add custom pages to the site navigation bar, entries can be added to the headerLinks of siteConfig.js. For example, if we have a page within website/pages/help.js, we can link to it by adding the following:

-
headerLinks: [
+
headerLinks: [
+  ...
+  { page: 'help', label: 'Help' },
   ...
-  { page: 'help', label: 'Help' },
-  ...
 ],
 

 
A label called Help will be added to the site navigation bar and when you click on it at the top of your site, the content from the help.js page will be shown.

 
Adding External Links

 
Custom links can be added to the site navigation bar with the following entry in siteConfig.js:

-
headerLinks: [
+
headerLinks: [
+  ...
+  { href: 'https://github.com/facebook/Docusaurus', label: 'GitHub' },
   ...
-  { href: 'https://github.com/facebook/Docusaurus', label: 'GitHub' },
-  ...
 ],
 

 
A label called GitHub will be added to the site navigation bar and when you click on it at the top of your site, the content of the external link will be shown.

diff --git a/docs/en/1.0.11/translation.html b/docs/en/1.0.11/translation.html
index c379f05b78..a5037e638f 100644
--- a/docs/en/1.0.11/translation.html
+++ b/docs/en/1.0.11/translation.html
@@ -79,8 +79,8 @@
         
Edit
Translations & Localization
Docusaurus allows for easy translation functionality using Crowdin. Documentation files written in English are uploaded to Crowdin for translation by users within a community. Top-level pages written with English strings can be translated by wrapping any strings you want to translate in a <translate> tag. Other titles and labels will also be found and properly translated.

 
Docusaurus Translation Configurations

 
To generate example files for translations with Docusaurus, run the examples script with the command line argument translations:

-
npm run examples translations
-

+
npm run examples translations
+

 
or

 
yarn examples translations
 

diff --git a/docs/en/1.0.11/translation/index.html b/docs/en/1.0.11/translation/index.html
index c379f05b78..a5037e638f 100644
--- a/docs/en/1.0.11/translation/index.html
+++ b/docs/en/1.0.11/translation/index.html
@@ -79,8 +79,8 @@
         
Edit
Translations & Localization
Docusaurus allows for easy translation functionality using Crowdin. Documentation files written in English are uploaded to Crowdin for translation by users within a community. Top-level pages written with English strings can be translated by wrapping any strings you want to translate in a <translate> tag. Other titles and labels will also be found and properly translated.

 
Docusaurus Translation Configurations

 
To generate example files for translations with Docusaurus, run the examples script with the command line argument translations:

-
npm run examples translations
-

+
npm run examples translations
+

 
or

 
yarn examples translations
 

diff --git a/docs/en/1.0.12/commands.html b/docs/en/1.0.12/commands.html
index df28637872..5bbc9e0859 100644
--- a/docs/en/1.0.12/commands.html
+++ b/docs/en/1.0.12/commands.html
@@ -83,19 +83,19 @@
 
 
Running from the command line

 
The scripts can be run using either Yarn or npm. If you've already gone through our Getting Started guide, you may already be familiar with the start command. It's the command that tells Docusaurus to run the docusaurus-start script which generates the site and starts up a server, and it's usually invoked like so:

-
yarn run start
-

+
yarn run start
+

 
The same script can be invoked using npm:

-
npm run start
-

+
npm run start
+

 
To run a particular script, just replace the start command in the examples above with the command associated with your script.

 
Using arguments

 
Some commands support optional arguments. For example, to start a server on port 8080, you can specify the --port argument when running start:

-
yarn run start --port 8080
-

+
yarn run start --port 8080
+

 
If you run Docusaurus using npm, you can still use the command line arguments by inserting a -- between npm run <command> and the command arguments:

-
npm run start -- --port 8080
-

+
npm run start -- --port 8080
+

 
Configuration

 
These scripts are set up under the "scripts" key in your website/package.json file as part of the installation process. If you need help setting them up again, please refer to the Installation guide.

 
Docusaurus provides some default mappings to allow you to run commands following Node conventions. Instead of typing docusaurus-start every time, you can type yarn run start or npm start to achieve the same.

diff --git a/docs/en/1.0.12/commands/index.html b/docs/en/1.0.12/commands/index.html
index df28637872..5bbc9e0859 100644
--- a/docs/en/1.0.12/commands/index.html
+++ b/docs/en/1.0.12/commands/index.html
@@ -83,19 +83,19 @@
 
 
Running from the command line

 
The scripts can be run using either Yarn or npm. If you've already gone through our Getting Started guide, you may already be familiar with the start command. It's the command that tells Docusaurus to run the docusaurus-start script which generates the site and starts up a server, and it's usually invoked like so:

-
yarn run start
-

+
yarn run start
+

 
The same script can be invoked using npm:

-
npm run start
-

+
npm run start
+

 
To run a particular script, just replace the start command in the examples above with the command associated with your script.

 
Using arguments

 
Some commands support optional arguments. For example, to start a server on port 8080, you can specify the --port argument when running start:

-
yarn run start --port 8080
-

+
yarn run start --port 8080
+

 
If you run Docusaurus using npm, you can still use the command line arguments by inserting a -- between npm run <command> and the command arguments:

-
npm run start -- --port 8080
-

+
npm run start -- --port 8080
+

 
Configuration

 
These scripts are set up under the "scripts" key in your website/package.json file as part of the installation process. If you need help setting them up again, please refer to the Installation guide.

 
Docusaurus provides some default mappings to allow you to run commands following Node conventions. Instead of typing docusaurus-start every time, you can type yarn run start or npm start to achieve the same.

diff --git a/docs/en/1.0.12/navigation.html b/docs/en/1.0.12/navigation.html
index cf05923a58..05b103f656 100644
--- a/docs/en/1.0.12/navigation.html
+++ b/docs/en/1.0.12/navigation.html
@@ -138,28 +138,28 @@
 
To expose sidebars, you will add clickable labels to the site navigation bar at the top of the website. You can add documents, pages and external links.

 
Adding Documents

 
After creating a new sidebar for the site by adding it to sidebars.json, you can expose the new sidebar from the top navigation bar by editing the headerLinks field of siteConfig.js.

-
headerLinks: [
+
headerLinks: [
+  ...
+  { doc: 'my-examples', label: 'Examples' },
   ...
-  { doc: 'my-examples', label: 'Examples' },
-  ...
 ],
 

 
A label called Examples will be added to the site navigation bar and when you click on it at the top of your site, the examples-sidebar will be shown and the default document will be my-examples.

 
Adding Custom Pages

 
To add custom pages to the site navigation bar, entries can be added to the headerLinks of siteConfig.js. For example, if we have a page within website/pages/help.js, we can link to it by adding the following:

-
headerLinks: [
+
headerLinks: [
+  ...
+  { page: 'help', label: 'Help' },
   ...
-  { page: 'help', label: 'Help' },
-  ...
 ],
 

 
A label called Help will be added to the site navigation bar and when you click on it at the top of your site, the content from the help.js page will be shown.

 
Adding External Links

 
Custom links can be added to the site navigation bar with the following entry in siteConfig.js:

-
headerLinks: [
+
headerLinks: [
+  ...
+  { href: 'https://github.com/facebook/Docusaurus', label: 'GitHub' },
   ...
-  { href: 'https://github.com/facebook/Docusaurus', label: 'GitHub' },
-  ...
 ],
 

 
A label called GitHub will be added to the site navigation bar and when you click on it at the top of your site, the content of the external link will be shown.

diff --git a/docs/en/1.0.12/navigation/index.html b/docs/en/1.0.12/navigation/index.html
index cf05923a58..05b103f656 100644
--- a/docs/en/1.0.12/navigation/index.html
+++ b/docs/en/1.0.12/navigation/index.html
@@ -138,28 +138,28 @@
 
To expose sidebars, you will add clickable labels to the site navigation bar at the top of the website. You can add documents, pages and external links.

 
Adding Documents

 
After creating a new sidebar for the site by adding it to sidebars.json, you can expose the new sidebar from the top navigation bar by editing the headerLinks field of siteConfig.js.

-
headerLinks: [
+
headerLinks: [
+  ...
+  { doc: 'my-examples', label: 'Examples' },
   ...
-  { doc: 'my-examples', label: 'Examples' },
-  ...
 ],
 

 
A label called Examples will be added to the site navigation bar and when you click on it at the top of your site, the examples-sidebar will be shown and the default document will be my-examples.

 
Adding Custom Pages

 
To add custom pages to the site navigation bar, entries can be added to the headerLinks of siteConfig.js. For example, if we have a page within website/pages/help.js, we can link to it by adding the following:

-
headerLinks: [
+
headerLinks: [
+  ...
+  { page: 'help', label: 'Help' },
   ...
-  { page: 'help', label: 'Help' },
-  ...
 ],
 

 
A label called Help will be added to the site navigation bar and when you click on it at the top of your site, the content from the help.js page will be shown.

 
Adding External Links

 
Custom links can be added to the site navigation bar with the following entry in siteConfig.js:

-
headerLinks: [
+
headerLinks: [
+  ...
+  { href: 'https://github.com/facebook/Docusaurus', label: 'GitHub' },
   ...
-  { href: 'https://github.com/facebook/Docusaurus', label: 'GitHub' },
-  ...
 ],
 

 
A label called GitHub will be added to the site navigation bar and when you click on it at the top of your site, the content of the external link will be shown.

diff --git a/docs/en/1.0.12/translation.html b/docs/en/1.0.12/translation.html
index c685e2a765..117394778e 100644
--- a/docs/en/1.0.12/translation.html
+++ b/docs/en/1.0.12/translation.html
@@ -79,8 +79,8 @@
         
Edit
Translations & Localization
Docusaurus allows for easy translation functionality using Crowdin. Documentation files written in English are uploaded to Crowdin for translation by users within a community. Top-level pages written with English strings can be translated by wrapping any strings you want to translate in a <translate> tag. Other titles and labels will also be found and properly translated.

 
Docusaurus Translation Configurations

 
To generate example files for translations with Docusaurus, run the examples script with the command line argument translations:

-
npm run examples translations
-

+
npm run examples translations
+

 
or

 
yarn examples translations
 

diff --git a/docs/en/1.0.12/translation/index.html b/docs/en/1.0.12/translation/index.html
index c685e2a765..117394778e 100644
--- a/docs/en/1.0.12/translation/index.html
+++ b/docs/en/1.0.12/translation/index.html
@@ -79,8 +79,8 @@
         
Edit
Translations & Localization
Docusaurus allows for easy translation functionality using Crowdin. Documentation files written in English are uploaded to Crowdin for translation by users within a community. Top-level pages written with English strings can be translated by wrapping any strings you want to translate in a <translate> tag. Other titles and labels will also be found and properly translated.

 
Docusaurus Translation Configurations

 
To generate example files for translations with Docusaurus, run the examples script with the command line argument translations:

-
npm run examples translations
-

+
npm run examples translations
+

 
or

 
yarn examples translations
 

diff --git a/docs/en/1.0.13/commands.html b/docs/en/1.0.13/commands.html
index 20d466b13c..54b4690d7b 100644
--- a/docs/en/1.0.13/commands.html
+++ b/docs/en/1.0.13/commands.html
@@ -83,19 +83,19 @@
 
 
Running from the command line

 
The scripts can be run using either Yarn or npm. If you've already gone through our Getting Started guide, you may already be familiar with the start command. It's the command that tells Docusaurus to run the docusaurus-start script which generates the site and starts up a server, and it's usually invoked like so:

-
yarn run start
-

+
yarn run start
+

 
The same script can be invoked using npm:

-
npm run start
-

+
npm run start
+

 
To run a particular script, just replace the start command in the examples above with the command associated with your script.

 
Using arguments

 
Some commands support optional arguments. For example, to start a server on port 8080, you can specify the --port argument when running start:

-
yarn run start --port 8080
-

+
yarn run start --port 8080
+

 
If you run Docusaurus using npm, you can still use the command line arguments by inserting a -- between npm run <command> and the command arguments:

-
npm run start -- --port 8080
-

+
npm run start -- --port 8080
+

 
Configuration

 
These scripts are set up under the "scripts" key in your website/package.json file as part of the installation process. If you need help setting them up again, please refer to the Installation guide.

 
Docusaurus provides some default mappings to allow you to run commands following Node conventions. Instead of typing docusaurus-start every time, you can type yarn run start or npm start to achieve the same.

diff --git a/docs/en/1.0.13/commands/index.html b/docs/en/1.0.13/commands/index.html
index 20d466b13c..54b4690d7b 100644
--- a/docs/en/1.0.13/commands/index.html
+++ b/docs/en/1.0.13/commands/index.html
@@ -83,19 +83,19 @@
 
 
Running from the command line

 
The scripts can be run using either Yarn or npm. If you've already gone through our Getting Started guide, you may already be familiar with the start command. It's the command that tells Docusaurus to run the docusaurus-start script which generates the site and starts up a server, and it's usually invoked like so:

-
yarn run start
-

+
yarn run start
+

 
The same script can be invoked using npm:

-
npm run start
-

+
npm run start
+

 
To run a particular script, just replace the start command in the examples above with the command associated with your script.

 
Using arguments

 
Some commands support optional arguments. For example, to start a server on port 8080, you can specify the --port argument when running start:

-
yarn run start --port 8080
-

+
yarn run start --port 8080
+

 
If you run Docusaurus using npm, you can still use the command line arguments by inserting a -- between npm run <command> and the command arguments:

-
npm run start -- --port 8080
-

+
npm run start -- --port 8080
+

 
Configuration

 
These scripts are set up under the "scripts" key in your website/package.json file as part of the installation process. If you need help setting them up again, please refer to the Installation guide.

 
Docusaurus provides some default mappings to allow you to run commands following Node conventions. Instead of typing docusaurus-start every time, you can type yarn run start or npm start to achieve the same.

diff --git a/docs/en/1.0.13/navigation.html b/docs/en/1.0.13/navigation.html
index 97cc88ffc8..04b84e214a 100644
--- a/docs/en/1.0.13/navigation.html
+++ b/docs/en/1.0.13/navigation.html
@@ -138,28 +138,28 @@
 
To expose sidebars, you will add clickable labels to the site navigation bar at the top of the website. You can add documents, pages and external links.

 
Adding Documents

 
After creating a new sidebar for the site by adding it to sidebars.json, you can expose the new sidebar from the top navigation bar by editing the headerLinks field of siteConfig.js.

-
headerLinks: [
+
headerLinks: [
+  ...
+  { doc: 'my-examples', label: 'Examples' },
   ...
-  { doc: 'my-examples', label: 'Examples' },
-  ...
 ],
 

 
A label called Examples will be added to the site navigation bar and when you click on it at the top of your site, the examples-sidebar will be shown and the default document will be my-examples.

 
Adding Custom Pages

 
To add custom pages to the site navigation bar, entries can be added to the headerLinks of siteConfig.js. For example, if we have a page within website/pages/help.js, we can link to it by adding the following:

-
headerLinks: [
+
headerLinks: [
+  ...
+  { page: 'help', label: 'Help' },
   ...
-  { page: 'help', label: 'Help' },
-  ...
 ],
 

 
A label called Help will be added to the site navigation bar and when you click on it at the top of your site, the content from the help.js page will be shown.

 
Adding External Links

 
Custom links can be added to the site navigation bar with the following entry in siteConfig.js:

-
headerLinks: [
+
headerLinks: [
+  ...
+  { href: 'https://github.com/facebook/Docusaurus', label: 'GitHub' },
   ...
-  { href: 'https://github.com/facebook/Docusaurus', label: 'GitHub' },
-  ...
 ],
 

 
A label called GitHub will be added to the site navigation bar and when you click on it at the top of your site, the content of the external link will be shown.

diff --git a/docs/en/1.0.13/navigation/index.html b/docs/en/1.0.13/navigation/index.html
index 97cc88ffc8..04b84e214a 100644
--- a/docs/en/1.0.13/navigation/index.html
+++ b/docs/en/1.0.13/navigation/index.html
@@ -138,28 +138,28 @@
 
To expose sidebars, you will add clickable labels to the site navigation bar at the top of the website. You can add documents, pages and external links.

 
Adding Documents

 
After creating a new sidebar for the site by adding it to sidebars.json, you can expose the new sidebar from the top navigation bar by editing the headerLinks field of siteConfig.js.

-
headerLinks: [
+
headerLinks: [
+  ...
+  { doc: 'my-examples', label: 'Examples' },
   ...
-  { doc: 'my-examples', label: 'Examples' },
-  ...
 ],
 

 
A label called Examples will be added to the site navigation bar and when you click on it at the top of your site, the examples-sidebar will be shown and the default document will be my-examples.

 
Adding Custom Pages

 
To add custom pages to the site navigation bar, entries can be added to the headerLinks of siteConfig.js. For example, if we have a page within website/pages/help.js, we can link to it by adding the following:

-
headerLinks: [
+
headerLinks: [
+  ...
+  { page: 'help', label: 'Help' },
   ...
-  { page: 'help', label: 'Help' },
-  ...
 ],
 

 
A label called Help will be added to the site navigation bar and when you click on it at the top of your site, the content from the help.js page will be shown.

 
Adding External Links

 
Custom links can be added to the site navigation bar with the following entry in siteConfig.js:

-
headerLinks: [
+
headerLinks: [
+  ...
+  { href: 'https://github.com/facebook/Docusaurus', label: 'GitHub' },
   ...
-  { href: 'https://github.com/facebook/Docusaurus', label: 'GitHub' },
-  ...
 ],
 

 
A label called GitHub will be added to the site navigation bar and when you click on it at the top of your site, the content of the external link will be shown.

diff --git a/docs/en/1.0.13/translation.html b/docs/en/1.0.13/translation.html
index 66d634ed7d..8d201d3605 100644
--- a/docs/en/1.0.13/translation.html
+++ b/docs/en/1.0.13/translation.html
@@ -79,8 +79,8 @@
         
Edit
Translations & Localization
Docusaurus allows for easy translation functionality using Crowdin. Documentation files written in English are uploaded to Crowdin for translation by users within a community. Top-level pages written with English strings can be translated by wrapping any strings you want to translate in a <translate> tag. Other titles and labels will also be found and properly translated.

 
Docusaurus Translation Configurations

 
To generate example files for translations with Docusaurus, run the examples script with the command line argument translations:

-
npm run examples translations
-

+
npm run examples translations
+

 
or

 
yarn examples translations
 

diff --git a/docs/en/1.0.13/translation/index.html b/docs/en/1.0.13/translation/index.html
index 66d634ed7d..8d201d3605 100644
--- a/docs/en/1.0.13/translation/index.html
+++ b/docs/en/1.0.13/translation/index.html
@@ -79,8 +79,8 @@
         
Edit
Translations & Localization
Docusaurus allows for easy translation functionality using Crowdin. Documentation files written in English are uploaded to Crowdin for translation by users within a community. Top-level pages written with English strings can be translated by wrapping any strings you want to translate in a <translate> tag. Other titles and labels will also be found and properly translated.

 
Docusaurus Translation Configurations

 
To generate example files for translations with Docusaurus, run the examples script with the command line argument translations:

-
npm run examples translations
-

+
npm run examples translations
+

 
or

 
yarn examples translations
 

diff --git a/docs/en/1.0.14/commands.html b/docs/en/1.0.14/commands.html
index a78027fca4..c5998edc12 100644
--- a/docs/en/1.0.14/commands.html
+++ b/docs/en/1.0.14/commands.html
@@ -83,19 +83,19 @@
 
 
Running from the command line

 
The scripts can be run using either Yarn or npm. If you've already gone through our Getting Started guide, you may already be familiar with the start command. It's the command that tells Docusaurus to run the docusaurus-start script which generates the site and starts up a server, and it's usually invoked like so:

-
yarn run start
-

+
yarn run start
+

 
The same script can be invoked using npm:

-
npm run start
-

+
npm run start
+

 
To run a particular script, just replace the start command in the examples above with the command associated with your script.

 
Using arguments

 
Some commands support optional arguments. For example, to start a server on port 8080, you can specify the --port argument when running start:

-
yarn run start --port 8080
-

+
yarn run start --port 8080
+

 
If you run Docusaurus using npm, you can still use the command line arguments by inserting a -- between npm run <command> and the command arguments:

-
npm run start -- --port 8080
-

+
npm run start -- --port 8080
+

 
Configuration

 
These scripts are set up under the "scripts" key in your website/package.json file as part of the installation process. If you need help setting them up again, please refer to the Installation guide.

 
Docusaurus provides some default mappings to allow you to run commands following Node conventions. Instead of typing docusaurus-start every time, you can type yarn run start or npm start to achieve the same.

diff --git a/docs/en/1.0.14/commands/index.html b/docs/en/1.0.14/commands/index.html
index a78027fca4..c5998edc12 100644
--- a/docs/en/1.0.14/commands/index.html
+++ b/docs/en/1.0.14/commands/index.html
@@ -83,19 +83,19 @@
 
 
Running from the command line

 
The scripts can be run using either Yarn or npm. If you've already gone through our Getting Started guide, you may already be familiar with the start command. It's the command that tells Docusaurus to run the docusaurus-start script which generates the site and starts up a server, and it's usually invoked like so:

-
yarn run start
-

+
yarn run start
+

 
The same script can be invoked using npm:

-
npm run start
-

+
npm run start
+

 
To run a particular script, just replace the start command in the examples above with the command associated with your script.

 
Using arguments

 
Some commands support optional arguments. For example, to start a server on port 8080, you can specify the --port argument when running start:

-
yarn run start --port 8080
-

+
yarn run start --port 8080
+

 
If you run Docusaurus using npm, you can still use the command line arguments by inserting a -- between npm run <command> and the command arguments:

-
npm run start -- --port 8080
-

+
npm run start -- --port 8080
+

 
Configuration

 
These scripts are set up under the "scripts" key in your website/package.json file as part of the installation process. If you need help setting them up again, please refer to the Installation guide.

 
Docusaurus provides some default mappings to allow you to run commands following Node conventions. Instead of typing docusaurus-start every time, you can type yarn run start or npm start to achieve the same.

diff --git a/docs/en/1.0.14/navigation.html b/docs/en/1.0.14/navigation.html
index 17d07c7356..bab1b57c16 100644
--- a/docs/en/1.0.14/navigation.html
+++ b/docs/en/1.0.14/navigation.html
@@ -138,28 +138,28 @@
 
To expose sidebars, you will add clickable labels to the site navigation bar at the top of the website. You can add documents, pages and external links.

 
Adding Documents

 
After creating a new sidebar for the site by adding it to sidebars.json, you can expose the new sidebar from the top navigation bar by editing the headerLinks field of siteConfig.js.

-
headerLinks: [
+
headerLinks: [
+  ...
+  { doc: 'my-examples', label: 'Examples' },
   ...
-  { doc: 'my-examples', label: 'Examples' },
-  ...
 ],
 

 
A label called Examples will be added to the site navigation bar and when you click on it at the top of your site, the examples-sidebar will be shown and the default document will be my-examples.

 
Adding Custom Pages

 
To add custom pages to the site navigation bar, entries can be added to the headerLinks of siteConfig.js. For example, if we have a page within website/pages/help.js, we can link to it by adding the following:

-
headerLinks: [
+
headerLinks: [
+  ...
+  { page: 'help', label: 'Help' },
   ...
-  { page: 'help', label: 'Help' },
-  ...
 ],
 

 
A label called Help will be added to the site navigation bar and when you click on it at the top of your site, the content from the help.js page will be shown.

 
Adding External Links

 
Custom links can be added to the site navigation bar with the following entry in siteConfig.js:

-
headerLinks: [
+
headerLinks: [
+  ...
+  { href: 'https://github.com/facebook/Docusaurus', label: 'GitHub' },
   ...
-  { href: 'https://github.com/facebook/Docusaurus', label: 'GitHub' },
-  ...
 ],
 

 
A label called GitHub will be added to the site navigation bar and when you click on it at the top of your site, the content of the external link will be shown.

diff --git a/docs/en/1.0.14/navigation/index.html b/docs/en/1.0.14/navigation/index.html
index 17d07c7356..bab1b57c16 100644
--- a/docs/en/1.0.14/navigation/index.html
+++ b/docs/en/1.0.14/navigation/index.html
@@ -138,28 +138,28 @@
 
To expose sidebars, you will add clickable labels to the site navigation bar at the top of the website. You can add documents, pages and external links.

 
Adding Documents

 
After creating a new sidebar for the site by adding it to sidebars.json, you can expose the new sidebar from the top navigation bar by editing the headerLinks field of siteConfig.js.

-
headerLinks: [
+
headerLinks: [
+  ...
+  { doc: 'my-examples', label: 'Examples' },
   ...
-  { doc: 'my-examples', label: 'Examples' },
-  ...
 ],
 

 
A label called Examples will be added to the site navigation bar and when you click on it at the top of your site, the examples-sidebar will be shown and the default document will be my-examples.

 
Adding Custom Pages

 
To add custom pages to the site navigation bar, entries can be added to the headerLinks of siteConfig.js. For example, if we have a page within website/pages/help.js, we can link to it by adding the following:

-
headerLinks: [
+
headerLinks: [
+  ...
+  { page: 'help', label: 'Help' },
   ...
-  { page: 'help', label: 'Help' },
-  ...
 ],
 

 
A label called Help will be added to the site navigation bar and when you click on it at the top of your site, the content from the help.js page will be shown.

 
Adding External Links

 
Custom links can be added to the site navigation bar with the following entry in siteConfig.js:

-
headerLinks: [
+
headerLinks: [
+  ...
+  { href: 'https://github.com/facebook/Docusaurus', label: 'GitHub' },
   ...
-  { href: 'https://github.com/facebook/Docusaurus', label: 'GitHub' },
-  ...
 ],
 

 
A label called GitHub will be added to the site navigation bar and when you click on it at the top of your site, the content of the external link will be shown.

diff --git a/docs/en/1.0.14/translation.html b/docs/en/1.0.14/translation.html
index 1ecc0265ba..d624499540 100644
--- a/docs/en/1.0.14/translation.html
+++ b/docs/en/1.0.14/translation.html
@@ -79,8 +79,8 @@
         
Edit
Translations & Localization
Docusaurus allows for easy translation functionality using Crowdin. Documentation files written in English are uploaded to Crowdin for translation by users within a community. Top-level pages written with English strings can be translated by wrapping any strings you want to translate in a <translate> tag. Other titles and labels will also be found and properly translated.

 
Docusaurus Translation Configurations

 
To generate example files for translations with Docusaurus, run the examples script with the command line argument translations:

-
npm run examples translations
-

+
npm run examples translations
+

 
or

 
yarn examples translations
 

diff --git a/docs/en/1.0.14/translation/index.html b/docs/en/1.0.14/translation/index.html
index 1ecc0265ba..d624499540 100644
--- a/docs/en/1.0.14/translation/index.html
+++ b/docs/en/1.0.14/translation/index.html
@@ -79,8 +79,8 @@
         
Edit
Translations & Localization
Docusaurus allows for easy translation functionality using Crowdin. Documentation files written in English are uploaded to Crowdin for translation by users within a community. Top-level pages written with English strings can be translated by wrapping any strings you want to translate in a <translate> tag. Other titles and labels will also be found and properly translated.

 
Docusaurus Translation Configurations

 
To generate example files for translations with Docusaurus, run the examples script with the command line argument translations:

-
npm run examples translations
-

+
npm run examples translations
+

 
or

 
yarn examples translations
 

diff --git a/docs/en/1.2.1/installation.html b/docs/en/1.2.1/installation.html
index 7d3cab48df..3b7787c0ec 100644
--- a/docs/en/1.2.1/installation.html
+++ b/docs/en/1.2.1/installation.html
@@ -130,17 +130,17 @@ yarn start (or npm run start)
 
After Docusaurus is installed, moving forward, you can check your current version of Docusaurus by going into the website directory and typing yarn outdated docusaurus or npm outdated docusaurus.

 
You will see something like this:

 
$ yarn outdated
-Using globally installed version of Yarn
-yarn outdated v1.5.1
-warning package.json: No license field
-warning No license field
-info Color legend : 
- "<red>"    : Major Update backward-incompatible updates 
- "<yellow>" : Minor Update backward-compatible features 
- "<green>"  : Patch Update backward-compatible bug fixes
-Package    Current Wanted Latest Package Type    URL                                          
-docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
-✨  Done in 0.41s.
+Using globally installed version of Yarn
+yarn outdated v1.5.1
+warning package.json: No license field
+warning No license field
+info Color legend : 
+ "<red>"    : Major Update backward-incompatible updates 
+ "<yellow>" : Minor Update backward-compatible features 
+ "<green>"  : Patch Update backward-compatible bug fixes
+Package    Current Wanted Latest Package Type    URL                                          
+docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
+✨  Done in 0.41s.
 

 

 
If there is no noticeable version output from the outdated commands, then you are up-to-date.

diff --git a/docs/en/1.2.1/installation/index.html b/docs/en/1.2.1/installation/index.html
index 7d3cab48df..3b7787c0ec 100644
--- a/docs/en/1.2.1/installation/index.html
+++ b/docs/en/1.2.1/installation/index.html
@@ -130,17 +130,17 @@ yarn start (or npm run start)
 
After Docusaurus is installed, moving forward, you can check your current version of Docusaurus by going into the website directory and typing yarn outdated docusaurus or npm outdated docusaurus.

 
You will see something like this:

 
$ yarn outdated
-Using globally installed version of Yarn
-yarn outdated v1.5.1
-warning package.json: No license field
-warning No license field
-info Color legend : 
- "<red>"    : Major Update backward-incompatible updates 
- "<yellow>" : Minor Update backward-compatible features 
- "<green>"  : Patch Update backward-compatible bug fixes
-Package    Current Wanted Latest Package Type    URL                                          
-docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
-✨  Done in 0.41s.
+Using globally installed version of Yarn
+yarn outdated v1.5.1
+warning package.json: No license field
+warning No license field
+info Color legend : 
+ "<red>"    : Major Update backward-incompatible updates 
+ "<yellow>" : Minor Update backward-compatible features 
+ "<green>"  : Patch Update backward-compatible bug fixes
+Package    Current Wanted Latest Package Type    URL                                          
+docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
+✨  Done in 0.41s.
 

 

 
If there is no noticeable version output from the outdated commands, then you are up-to-date.

diff --git a/docs/en/1.3.0/installation.html b/docs/en/1.3.0/installation.html
index 1edd7144d9..b50638e620 100644
--- a/docs/en/1.3.0/installation.html
+++ b/docs/en/1.3.0/installation.html
@@ -130,17 +130,17 @@ yarn start (or npm run start)
 
After Docusaurus is installed, moving forward, you can check your current version of Docusaurus by going into the website directory and typing yarn outdated docusaurus or npm outdated docusaurus.

 
You will see something like this:

 
$ yarn outdated
-Using globally installed version of Yarn
-yarn outdated v1.5.1
-warning package.json: No license field
-warning No license field
-info Color legend : 
- "<red>"    : Major Update backward-incompatible updates 
- "<yellow>" : Minor Update backward-compatible features 
- "<green>"  : Patch Update backward-compatible bug fixes
-Package    Current Wanted Latest Package Type    URL                                          
-docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
-✨  Done in 0.41s.
+Using globally installed version of Yarn
+yarn outdated v1.5.1
+warning package.json: No license field
+warning No license field
+info Color legend : 
+ "<red>"    : Major Update backward-incompatible updates 
+ "<yellow>" : Minor Update backward-compatible features 
+ "<green>"  : Patch Update backward-compatible bug fixes
+Package    Current Wanted Latest Package Type    URL                                          
+docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
+✨  Done in 0.41s.
 

 

 
If there is no noticeable version output from the outdated commands, then you are up-to-date.

diff --git a/docs/en/1.3.0/installation/index.html b/docs/en/1.3.0/installation/index.html
index 1edd7144d9..b50638e620 100644
--- a/docs/en/1.3.0/installation/index.html
+++ b/docs/en/1.3.0/installation/index.html
@@ -130,17 +130,17 @@ yarn start (or npm run start)
 
After Docusaurus is installed, moving forward, you can check your current version of Docusaurus by going into the website directory and typing yarn outdated docusaurus or npm outdated docusaurus.

 
You will see something like this:

 
$ yarn outdated
-Using globally installed version of Yarn
-yarn outdated v1.5.1
-warning package.json: No license field
-warning No license field
-info Color legend : 
- "<red>"    : Major Update backward-incompatible updates 
- "<yellow>" : Minor Update backward-compatible features 
- "<green>"  : Patch Update backward-compatible bug fixes
-Package    Current Wanted Latest Package Type    URL                                          
-docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
-✨  Done in 0.41s.
+Using globally installed version of Yarn
+yarn outdated v1.5.1
+warning package.json: No license field
+warning No license field
+info Color legend : 
+ "<red>"    : Major Update backward-incompatible updates 
+ "<yellow>" : Minor Update backward-compatible features 
+ "<green>"  : Patch Update backward-compatible bug fixes
+Package    Current Wanted Latest Package Type    URL                                          
+docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
+✨  Done in 0.41s.
 

 

 
If there is no noticeable version output from the outdated commands, then you are up-to-date.

diff --git a/docs/en/1.3.1/installation.html b/docs/en/1.3.1/installation.html
index 8c04c138fe..4ef3bd6b78 100644
--- a/docs/en/1.3.1/installation.html
+++ b/docs/en/1.3.1/installation.html
@@ -130,17 +130,17 @@ yarn start (or npm run start)
 
After Docusaurus is installed, moving forward, you can check your current version of Docusaurus by going into the website directory and typing yarn outdated docusaurus or npm outdated docusaurus.

 
You will see something like this:

 
$ yarn outdated
-Using globally installed version of Yarn
-yarn outdated v1.5.1
-warning package.json: No license field
-warning No license field
-info Color legend : 
- "<red>"    : Major Update backward-incompatible updates 
- "<yellow>" : Minor Update backward-compatible features 
- "<green>"  : Patch Update backward-compatible bug fixes
-Package    Current Wanted Latest Package Type    URL                                          
-docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
-✨  Done in 0.41s.
+Using globally installed version of Yarn
+yarn outdated v1.5.1
+warning package.json: No license field
+warning No license field
+info Color legend : 
+ "<red>"    : Major Update backward-incompatible updates 
+ "<yellow>" : Minor Update backward-compatible features 
+ "<green>"  : Patch Update backward-compatible bug fixes
+Package    Current Wanted Latest Package Type    URL                                          
+docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
+✨  Done in 0.41s.
 

 

 
If there is no noticeable version output from the outdated commands, then you are up-to-date.

diff --git a/docs/en/1.3.1/installation/index.html b/docs/en/1.3.1/installation/index.html
index 8c04c138fe..4ef3bd6b78 100644
--- a/docs/en/1.3.1/installation/index.html
+++ b/docs/en/1.3.1/installation/index.html
@@ -130,17 +130,17 @@ yarn start (or npm run start)
 
After Docusaurus is installed, moving forward, you can check your current version of Docusaurus by going into the website directory and typing yarn outdated docusaurus or npm outdated docusaurus.

 
You will see something like this:

 
$ yarn outdated
-Using globally installed version of Yarn
-yarn outdated v1.5.1
-warning package.json: No license field
-warning No license field
-info Color legend : 
- "<red>"    : Major Update backward-incompatible updates 
- "<yellow>" : Minor Update backward-compatible features 
- "<green>"  : Patch Update backward-compatible bug fixes
-Package    Current Wanted Latest Package Type    URL                                          
-docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
-✨  Done in 0.41s.
+Using globally installed version of Yarn
+yarn outdated v1.5.1
+warning package.json: No license field
+warning No license field
+info Color legend : 
+ "<red>"    : Major Update backward-incompatible updates 
+ "<yellow>" : Minor Update backward-compatible features 
+ "<green>"  : Patch Update backward-compatible bug fixes
+Package    Current Wanted Latest Package Type    URL                                          
+docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
+✨  Done in 0.41s.
 

 

 
If there is no noticeable version output from the outdated commands, then you are up-to-date.

diff --git a/docs/en/1.3.2/installation.html b/docs/en/1.3.2/installation.html
index 6595c90980..e4aca95207 100644
--- a/docs/en/1.3.2/installation.html
+++ b/docs/en/1.3.2/installation.html
@@ -130,17 +130,17 @@ yarn start (or npm run start)
 
After Docusaurus is installed, moving forward, you can check your current version of Docusaurus by going into the website directory and typing yarn outdated docusaurus or npm outdated docusaurus.

 
You will see something like this:

 
$ yarn outdated
-Using globally installed version of Yarn
-yarn outdated v1.5.1
-warning package.json: No license field
-warning No license field
-info Color legend : 
- "<red>"    : Major Update backward-incompatible updates 
- "<yellow>" : Minor Update backward-compatible features 
- "<green>"  : Patch Update backward-compatible bug fixes
-Package    Current Wanted Latest Package Type    URL                                          
-docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
-✨  Done in 0.41s.
+Using globally installed version of Yarn
+yarn outdated v1.5.1
+warning package.json: No license field
+warning No license field
+info Color legend : 
+ "<red>"    : Major Update backward-incompatible updates 
+ "<yellow>" : Minor Update backward-compatible features 
+ "<green>"  : Patch Update backward-compatible bug fixes
+Package    Current Wanted Latest Package Type    URL                                          
+docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
+✨  Done in 0.41s.
 

 

 
If there is no noticeable version output from the outdated commands, then you are up-to-date.

diff --git a/docs/en/1.3.2/installation/index.html b/docs/en/1.3.2/installation/index.html
index 6595c90980..e4aca95207 100644
--- a/docs/en/1.3.2/installation/index.html
+++ b/docs/en/1.3.2/installation/index.html
@@ -130,17 +130,17 @@ yarn start (or npm run start)
 
After Docusaurus is installed, moving forward, you can check your current version of Docusaurus by going into the website directory and typing yarn outdated docusaurus or npm outdated docusaurus.

 
You will see something like this:

 
$ yarn outdated
-Using globally installed version of Yarn
-yarn outdated v1.5.1
-warning package.json: No license field
-warning No license field
-info Color legend : 
- "<red>"    : Major Update backward-incompatible updates 
- "<yellow>" : Minor Update backward-compatible features 
- "<green>"  : Patch Update backward-compatible bug fixes
-Package    Current Wanted Latest Package Type    URL                                          
-docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
-✨  Done in 0.41s.
+Using globally installed version of Yarn
+yarn outdated v1.5.1
+warning package.json: No license field
+warning No license field
+info Color legend : 
+ "<red>"    : Major Update backward-incompatible updates 
+ "<yellow>" : Minor Update backward-compatible features 
+ "<green>"  : Patch Update backward-compatible bug fixes
+Package    Current Wanted Latest Package Type    URL                                          
+docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
+✨  Done in 0.41s.
 

 

 
If there is no noticeable version output from the outdated commands, then you are up-to-date.

diff --git a/docs/en/1.3.3/installation.html b/docs/en/1.3.3/installation.html
index f65c21cd6d..9eb5a68c2d 100644
--- a/docs/en/1.3.3/installation.html
+++ b/docs/en/1.3.3/installation.html
@@ -144,17 +144,17 @@ yarn start (or npm run start)
 
At any time after Docusaurus is installed, you can check your current version of Docusaurus by going into the website directory and typing yarn outdated docusaurus or npm outdated docusaurus.

 
You will see something like this:

 
$ yarn outdated
-Using globally installed version of Yarn
-yarn outdated v1.5.1
-warning package.json: No license field
-warning No license field
-info Color legend : 
- "<red>"    : Major Update backward-incompatible updates 
- "<yellow>" : Minor Update backward-compatible features 
- "<green>"  : Patch Update backward-compatible bug fixes
-Package    Current Wanted Latest Package Type    URL                                          
-docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
-✨  Done in 0.41s.
+Using globally installed version of Yarn
+yarn outdated v1.5.1
+warning package.json: No license field
+warning No license field
+info Color legend : 
+ "<red>"    : Major Update backward-incompatible updates 
+ "<yellow>" : Minor Update backward-compatible features 
+ "<green>"  : Patch Update backward-compatible bug fixes
+Package    Current Wanted Latest Package Type    URL                                          
+docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
+✨  Done in 0.41s.
 

 

 
If there is no noticeable version output from the outdated commands, then you are up-to-date.

diff --git a/docs/en/1.3.3/installation/index.html b/docs/en/1.3.3/installation/index.html
index f65c21cd6d..9eb5a68c2d 100644
--- a/docs/en/1.3.3/installation/index.html
+++ b/docs/en/1.3.3/installation/index.html
@@ -144,17 +144,17 @@ yarn start (or npm run start)
 
At any time after Docusaurus is installed, you can check your current version of Docusaurus by going into the website directory and typing yarn outdated docusaurus or npm outdated docusaurus.

 
You will see something like this:

 
$ yarn outdated
-Using globally installed version of Yarn
-yarn outdated v1.5.1
-warning package.json: No license field
-warning No license field
-info Color legend : 
- "<red>"    : Major Update backward-incompatible updates 
- "<yellow>" : Minor Update backward-compatible features 
- "<green>"  : Patch Update backward-compatible bug fixes
-Package    Current Wanted Latest Package Type    URL                                          
-docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
-✨  Done in 0.41s.
+Using globally installed version of Yarn
+yarn outdated v1.5.1
+warning package.json: No license field
+warning No license field
+info Color legend : 
+ "<red>"    : Major Update backward-incompatible updates 
+ "<yellow>" : Minor Update backward-compatible features 
+ "<green>"  : Patch Update backward-compatible bug fixes
+Package    Current Wanted Latest Package Type    URL                                          
+docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
+✨  Done in 0.41s.
 

 

 
If there is no noticeable version output from the outdated commands, then you are up-to-date.

diff --git a/docs/en/1.4.0/installation.html b/docs/en/1.4.0/installation.html
index c75144f326..c1430ec024 100644
--- a/docs/en/1.4.0/installation.html
+++ b/docs/en/1.4.0/installation.html
@@ -144,17 +144,17 @@ yarn start (or npm run start)
 
At any time after Docusaurus is installed, you can check your current version of Docusaurus by going into the website directory and typing yarn outdated docusaurus or npm outdated docusaurus.

 
You will see something like this:

 
$ yarn outdated
-Using globally installed version of Yarn
-yarn outdated v1.5.1
-warning package.json: No license field
-warning No license field
-info Color legend : 
- "<red>"    : Major Update backward-incompatible updates 
- "<yellow>" : Minor Update backward-compatible features 
- "<green>"  : Patch Update backward-compatible bug fixes
-Package    Current Wanted Latest Package Type    URL                                          
-docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
-✨  Done in 0.41s.
+Using globally installed version of Yarn
+yarn outdated v1.5.1
+warning package.json: No license field
+warning No license field
+info Color legend : 
+ "<red>"    : Major Update backward-incompatible updates 
+ "<yellow>" : Minor Update backward-compatible features 
+ "<green>"  : Patch Update backward-compatible bug fixes
+Package    Current Wanted Latest Package Type    URL                                          
+docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
+✨  Done in 0.41s.
 

 

 
If there is no noticeable version output from the outdated commands, then you are up-to-date.

diff --git a/docs/en/1.4.0/installation/index.html b/docs/en/1.4.0/installation/index.html
index c75144f326..c1430ec024 100644
--- a/docs/en/1.4.0/installation/index.html
+++ b/docs/en/1.4.0/installation/index.html
@@ -144,17 +144,17 @@ yarn start (or npm run start)
 
At any time after Docusaurus is installed, you can check your current version of Docusaurus by going into the website directory and typing yarn outdated docusaurus or npm outdated docusaurus.

 
You will see something like this:

 
$ yarn outdated
-Using globally installed version of Yarn
-yarn outdated v1.5.1
-warning package.json: No license field
-warning No license field
-info Color legend : 
- "<red>"    : Major Update backward-incompatible updates 
- "<yellow>" : Minor Update backward-compatible features 
- "<green>"  : Patch Update backward-compatible bug fixes
-Package    Current Wanted Latest Package Type    URL                                          
-docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
-✨  Done in 0.41s.
+Using globally installed version of Yarn
+yarn outdated v1.5.1
+warning package.json: No license field
+warning No license field
+info Color legend : 
+ "<red>"    : Major Update backward-incompatible updates 
+ "<yellow>" : Minor Update backward-compatible features 
+ "<green>"  : Patch Update backward-compatible bug fixes
+Package    Current Wanted Latest Package Type    URL                                          
+docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
+✨  Done in 0.41s.
 

 

 
If there is no noticeable version output from the outdated commands, then you are up-to-date.

diff --git a/docs/en/1.5.0/installation.html b/docs/en/1.5.0/installation.html
index 9d7a99a794..4be76526fc 100644
--- a/docs/en/1.5.0/installation.html
+++ b/docs/en/1.5.0/installation.html
@@ -144,17 +144,17 @@ yarn start (or npm run start)
 
At any time after Docusaurus is installed, you can check your current version of Docusaurus by going into the website directory and typing yarn outdated docusaurus or npm outdated docusaurus.

 
You will see something like this:

 
$ yarn outdated
-Using globally installed version of Yarn
-yarn outdated v1.5.1
-warning package.json: No license field
-warning No license field
-info Color legend : 
- "<red>"    : Major Update backward-incompatible updates 
- "<yellow>" : Minor Update backward-compatible features 
- "<green>"  : Patch Update backward-compatible bug fixes
-Package    Current Wanted Latest Package Type    URL                                          
-docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
-✨  Done in 0.41s.
+Using globally installed version of Yarn
+yarn outdated v1.5.1
+warning package.json: No license field
+warning No license field
+info Color legend : 
+ "<red>"    : Major Update backward-incompatible updates 
+ "<yellow>" : Minor Update backward-compatible features 
+ "<green>"  : Patch Update backward-compatible bug fixes
+Package    Current Wanted Latest Package Type    URL                                          
+docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
+✨  Done in 0.41s.
 

 

 
If there is no noticeable version output from the outdated commands, then you are up-to-date.

diff --git a/docs/en/1.5.0/installation/index.html b/docs/en/1.5.0/installation/index.html
index 9d7a99a794..4be76526fc 100644
--- a/docs/en/1.5.0/installation/index.html
+++ b/docs/en/1.5.0/installation/index.html
@@ -144,17 +144,17 @@ yarn start (or npm run start)
 
At any time after Docusaurus is installed, you can check your current version of Docusaurus by going into the website directory and typing yarn outdated docusaurus or npm outdated docusaurus.

 
You will see something like this:

 
$ yarn outdated
-Using globally installed version of Yarn
-yarn outdated v1.5.1
-warning package.json: No license field
-warning No license field
-info Color legend : 
- "<red>"    : Major Update backward-incompatible updates 
- "<yellow>" : Minor Update backward-compatible features 
- "<green>"  : Patch Update backward-compatible bug fixes
-Package    Current Wanted Latest Package Type    URL                                          
-docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
-✨  Done in 0.41s.
+Using globally installed version of Yarn
+yarn outdated v1.5.1
+warning package.json: No license field
+warning No license field
+info Color legend : 
+ "<red>"    : Major Update backward-incompatible updates 
+ "<yellow>" : Minor Update backward-compatible features 
+ "<green>"  : Patch Update backward-compatible bug fixes
+Package    Current Wanted Latest Package Type    URL                                          
+docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
+✨  Done in 0.41s.
 

 

 
If there is no noticeable version output from the outdated commands, then you are up-to-date.

diff --git a/docs/en/1.5.1/installation.html b/docs/en/1.5.1/installation.html
index 4acaa0091d..416b32d3a4 100644
--- a/docs/en/1.5.1/installation.html
+++ b/docs/en/1.5.1/installation.html
@@ -144,17 +144,17 @@ yarn start (or npm run start)
 
At any time after Docusaurus is installed, you can check your current version of Docusaurus by going into the website directory and typing yarn outdated docusaurus or npm outdated docusaurus.

 
You will see something like this:

 
$ yarn outdated
-Using globally installed version of Yarn
-yarn outdated v1.5.1
-warning package.json: No license field
-warning No license field
-info Color legend : 
- "<red>"    : Major Update backward-incompatible updates 
- "<yellow>" : Minor Update backward-compatible features 
- "<green>"  : Patch Update backward-compatible bug fixes
-Package    Current Wanted Latest Package Type    URL                                          
-docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
-✨  Done in 0.41s.
+Using globally installed version of Yarn
+yarn outdated v1.5.1
+warning package.json: No license field
+warning No license field
+info Color legend : 
+ "<red>"    : Major Update backward-incompatible updates 
+ "<yellow>" : Minor Update backward-compatible features 
+ "<green>"  : Patch Update backward-compatible bug fixes
+Package    Current Wanted Latest Package Type    URL                                          
+docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
+✨  Done in 0.41s.
 

 

 
If there is no noticeable version output from the outdated commands, then you are up-to-date.

diff --git a/docs/en/1.5.1/installation/index.html b/docs/en/1.5.1/installation/index.html
index 4acaa0091d..416b32d3a4 100644
--- a/docs/en/1.5.1/installation/index.html
+++ b/docs/en/1.5.1/installation/index.html
@@ -144,17 +144,17 @@ yarn start (or npm run start)
 
At any time after Docusaurus is installed, you can check your current version of Docusaurus by going into the website directory and typing yarn outdated docusaurus or npm outdated docusaurus.

 
You will see something like this:

 
$ yarn outdated
-Using globally installed version of Yarn
-yarn outdated v1.5.1
-warning package.json: No license field
-warning No license field
-info Color legend : 
- "<red>"    : Major Update backward-incompatible updates 
- "<yellow>" : Minor Update backward-compatible features 
- "<green>"  : Patch Update backward-compatible bug fixes
-Package    Current Wanted Latest Package Type    URL                                          
-docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
-✨  Done in 0.41s.
+Using globally installed version of Yarn
+yarn outdated v1.5.1
+warning package.json: No license field
+warning No license field
+info Color legend : 
+ "<red>"    : Major Update backward-incompatible updates 
+ "<yellow>" : Minor Update backward-compatible features 
+ "<green>"  : Patch Update backward-compatible bug fixes
+Package    Current Wanted Latest Package Type    URL                                          
+docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
+✨  Done in 0.41s.
 

 

 
If there is no noticeable version output from the outdated commands, then you are up-to-date.

diff --git a/docs/en/1.6.0/installation.html b/docs/en/1.6.0/installation.html
index 399d53d524..b274ee49ea 100644
--- a/docs/en/1.6.0/installation.html
+++ b/docs/en/1.6.0/installation.html
@@ -144,17 +144,17 @@ yarn start (or npm run start)
 
At any time after Docusaurus is installed, you can check your current version of Docusaurus by going into the website directory and typing yarn outdated docusaurus or npm outdated docusaurus.

 
You will see something like this:

 
$ yarn outdated
-Using globally installed version of Yarn
-yarn outdated v1.5.1
-warning package.json: No license field
-warning No license field
-info Color legend : 
- "<red>"    : Major Update backward-incompatible updates 
- "<yellow>" : Minor Update backward-compatible features 
- "<green>"  : Patch Update backward-compatible bug fixes
-Package    Current Wanted Latest Package Type    URL                                          
-docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
-✨  Done in 0.41s.
+Using globally installed version of Yarn
+yarn outdated v1.5.1
+warning package.json: No license field
+warning No license field
+info Color legend : 
+ "<red>"    : Major Update backward-incompatible updates 
+ "<yellow>" : Minor Update backward-compatible features 
+ "<green>"  : Patch Update backward-compatible bug fixes
+Package    Current Wanted Latest Package Type    URL                                          
+docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
+✨  Done in 0.41s.
 

 

 
If there is no noticeable version output from the outdated commands, then you are up-to-date.

diff --git a/docs/en/1.6.0/installation/index.html b/docs/en/1.6.0/installation/index.html
index 399d53d524..b274ee49ea 100644
--- a/docs/en/1.6.0/installation/index.html
+++ b/docs/en/1.6.0/installation/index.html
@@ -144,17 +144,17 @@ yarn start (or npm run start)
 
At any time after Docusaurus is installed, you can check your current version of Docusaurus by going into the website directory and typing yarn outdated docusaurus or npm outdated docusaurus.

 
You will see something like this:

 
$ yarn outdated
-Using globally installed version of Yarn
-yarn outdated v1.5.1
-warning package.json: No license field
-warning No license field
-info Color legend : 
- "<red>"    : Major Update backward-incompatible updates 
- "<yellow>" : Minor Update backward-compatible features 
- "<green>"  : Patch Update backward-compatible bug fixes
-Package    Current Wanted Latest Package Type    URL                                          
-docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
-✨  Done in 0.41s.
+Using globally installed version of Yarn
+yarn outdated v1.5.1
+warning package.json: No license field
+warning No license field
+info Color legend : 
+ "<red>"    : Major Update backward-incompatible updates 
+ "<yellow>" : Minor Update backward-compatible features 
+ "<green>"  : Patch Update backward-compatible bug fixes
+Package    Current Wanted Latest Package Type    URL                                          
+docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
+✨  Done in 0.41s.
 

 

 
If there is no noticeable version output from the outdated commands, then you are up-to-date.

diff --git a/docs/en/1.6.1/installation.html b/docs/en/1.6.1/installation.html
index 41d5bc6ea5..9d6c36f07a 100644
--- a/docs/en/1.6.1/installation.html
+++ b/docs/en/1.6.1/installation.html
@@ -144,17 +144,17 @@ yarn start (or npm run start)
 
At any time after Docusaurus is installed, you can check your current version of Docusaurus by going into the website directory and typing yarn outdated docusaurus or npm outdated docusaurus.

 
You will see something like this:

 
$ yarn outdated
-Using globally installed version of Yarn
-yarn outdated v1.5.1
-warning package.json: No license field
-warning No license field
-info Color legend : 
- "<red>"    : Major Update backward-incompatible updates 
- "<yellow>" : Minor Update backward-compatible features 
- "<green>"  : Patch Update backward-compatible bug fixes
-Package    Current Wanted Latest Package Type    URL                                          
-docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
-✨  Done in 0.41s.
+Using globally installed version of Yarn
+yarn outdated v1.5.1
+warning package.json: No license field
+warning No license field
+info Color legend : 
+ "<red>"    : Major Update backward-incompatible updates 
+ "<yellow>" : Minor Update backward-compatible features 
+ "<green>"  : Patch Update backward-compatible bug fixes
+Package    Current Wanted Latest Package Type    URL                                          
+docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
+✨  Done in 0.41s.
 

 

 
If there is no noticeable version output from the outdated commands, then you are up-to-date.

diff --git a/docs/en/1.6.1/installation/index.html b/docs/en/1.6.1/installation/index.html
index 41d5bc6ea5..9d6c36f07a 100644
--- a/docs/en/1.6.1/installation/index.html
+++ b/docs/en/1.6.1/installation/index.html
@@ -144,17 +144,17 @@ yarn start (or npm run start)
 
At any time after Docusaurus is installed, you can check your current version of Docusaurus by going into the website directory and typing yarn outdated docusaurus or npm outdated docusaurus.

 
You will see something like this:

 
$ yarn outdated
-Using globally installed version of Yarn
-yarn outdated v1.5.1
-warning package.json: No license field
-warning No license field
-info Color legend : 
- "<red>"    : Major Update backward-incompatible updates 
- "<yellow>" : Minor Update backward-compatible features 
- "<green>"  : Patch Update backward-compatible bug fixes
-Package    Current Wanted Latest Package Type    URL                                          
-docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
-✨  Done in 0.41s.
+Using globally installed version of Yarn
+yarn outdated v1.5.1
+warning package.json: No license field
+warning No license field
+info Color legend : 
+ "<red>"    : Major Update backward-incompatible updates 
+ "<yellow>" : Minor Update backward-compatible features 
+ "<green>"  : Patch Update backward-compatible bug fixes
+Package    Current Wanted Latest Package Type    URL                                          
+docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
+✨  Done in 0.41s.
 

 

 
If there is no noticeable version output from the outdated commands, then you are up-to-date.

diff --git a/docs/en/1.6.2/installation.html b/docs/en/1.6.2/installation.html
index c7c6b804a8..4d8aa63c8e 100644
--- a/docs/en/1.6.2/installation.html
+++ b/docs/en/1.6.2/installation.html
@@ -144,17 +144,17 @@ yarn start (or npm run start)
 
At any time after Docusaurus is installed, you can check your current version of Docusaurus by going into the website directory and typing yarn outdated docusaurus or npm outdated docusaurus.

 
You will see something like this:

 
$ yarn outdated
-Using globally installed version of Yarn
-yarn outdated v1.5.1
-warning package.json: No license field
-warning No license field
-info Color legend : 
- "<red>"    : Major Update backward-incompatible updates 
- "<yellow>" : Minor Update backward-compatible features 
- "<green>"  : Patch Update backward-compatible bug fixes
-Package    Current Wanted Latest Package Type    URL                                          
-docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
-✨  Done in 0.41s.
+Using globally installed version of Yarn
+yarn outdated v1.5.1
+warning package.json: No license field
+warning No license field
+info Color legend : 
+ "<red>"    : Major Update backward-incompatible updates 
+ "<yellow>" : Minor Update backward-compatible features 
+ "<green>"  : Patch Update backward-compatible bug fixes
+Package    Current Wanted Latest Package Type    URL                                          
+docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
+✨  Done in 0.41s.
 

 

 
If there is no noticeable version output from the outdated commands, then you are up-to-date.

diff --git a/docs/en/1.6.2/installation/index.html b/docs/en/1.6.2/installation/index.html
index c7c6b804a8..4d8aa63c8e 100644
--- a/docs/en/1.6.2/installation/index.html
+++ b/docs/en/1.6.2/installation/index.html
@@ -144,17 +144,17 @@ yarn start (or npm run start)
 
At any time after Docusaurus is installed, you can check your current version of Docusaurus by going into the website directory and typing yarn outdated docusaurus or npm outdated docusaurus.

 
You will see something like this:

 
$ yarn outdated
-Using globally installed version of Yarn
-yarn outdated v1.5.1
-warning package.json: No license field
-warning No license field
-info Color legend : 
- "<red>"    : Major Update backward-incompatible updates 
- "<yellow>" : Minor Update backward-compatible features 
- "<green>"  : Patch Update backward-compatible bug fixes
-Package    Current Wanted Latest Package Type    URL                                          
-docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
-✨  Done in 0.41s.
+Using globally installed version of Yarn
+yarn outdated v1.5.1
+warning package.json: No license field
+warning No license field
+info Color legend : 
+ "<red>"    : Major Update backward-incompatible updates 
+ "<yellow>" : Minor Update backward-compatible features 
+ "<green>"  : Patch Update backward-compatible bug fixes
+Package    Current Wanted Latest Package Type    URL                                          
+docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
+✨  Done in 0.41s.
 

 

 
If there is no noticeable version output from the outdated commands, then you are up-to-date.

diff --git a/docs/en/1.7.0/installation.html b/docs/en/1.7.0/installation.html
index 6ed7488f56..6ed1c0820a 100644
--- a/docs/en/1.7.0/installation.html
+++ b/docs/en/1.7.0/installation.html
@@ -144,17 +144,17 @@ yarn start (or npm run start)
 
At any time after Docusaurus is installed, you can check your current version of Docusaurus by going into the website directory and typing yarn outdated docusaurus or npm outdated docusaurus.

 
You will see something like this:

 
$ yarn outdated
-Using globally installed version of Yarn
-yarn outdated v1.5.1
-warning package.json: No license field
-warning No license field
-info Color legend : 
- "<red>"    : Major Update backward-incompatible updates 
- "<yellow>" : Minor Update backward-compatible features 
- "<green>"  : Patch Update backward-compatible bug fixes
-Package    Current Wanted Latest Package Type    URL                                          
-docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
-✨  Done in 0.41s.
+Using globally installed version of Yarn
+yarn outdated v1.5.1
+warning package.json: No license field
+warning No license field
+info Color legend : 
+ "<red>"    : Major Update backward-incompatible updates 
+ "<yellow>" : Minor Update backward-compatible features 
+ "<green>"  : Patch Update backward-compatible bug fixes
+Package    Current Wanted Latest Package Type    URL                                          
+docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
+✨  Done in 0.41s.
 

 

 
If there is no noticeable version output from the outdated commands, then you are up-to-date.

diff --git a/docs/en/1.7.0/installation/index.html b/docs/en/1.7.0/installation/index.html
index 6ed7488f56..6ed1c0820a 100644
--- a/docs/en/1.7.0/installation/index.html
+++ b/docs/en/1.7.0/installation/index.html
@@ -144,17 +144,17 @@ yarn start (or npm run start)
 
At any time after Docusaurus is installed, you can check your current version of Docusaurus by going into the website directory and typing yarn outdated docusaurus or npm outdated docusaurus.

 
You will see something like this:

 
$ yarn outdated
-Using globally installed version of Yarn
-yarn outdated v1.5.1
-warning package.json: No license field
-warning No license field
-info Color legend : 
- "<red>"    : Major Update backward-incompatible updates 
- "<yellow>" : Minor Update backward-compatible features 
- "<green>"  : Patch Update backward-compatible bug fixes
-Package    Current Wanted Latest Package Type    URL                                          
-docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
-✨  Done in 0.41s.
+Using globally installed version of Yarn
+yarn outdated v1.5.1
+warning package.json: No license field
+warning No license field
+info Color legend : 
+ "<red>"    : Major Update backward-incompatible updates 
+ "<yellow>" : Minor Update backward-compatible features 
+ "<green>"  : Patch Update backward-compatible bug fixes
+Package    Current Wanted Latest Package Type    URL                                          
+docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
+✨  Done in 0.41s.
 

 

 
If there is no noticeable version output from the outdated commands, then you are up-to-date.

diff --git a/docs/en/1.7.1/installation.html b/docs/en/1.7.1/installation.html
index 3c0c95685d..9325226161 100644
--- a/docs/en/1.7.1/installation.html
+++ b/docs/en/1.7.1/installation.html
@@ -144,17 +144,17 @@ yarn start (or npm run start)
 
At any time after Docusaurus is installed, you can check your current version of Docusaurus by going into the website directory and typing yarn outdated docusaurus or npm outdated docusaurus.

 
You will see something like this:

 
$ yarn outdated
-Using globally installed version of Yarn
-yarn outdated v1.5.1
-warning package.json: No license field
-warning No license field
-info Color legend : 
- "<red>"    : Major Update backward-incompatible updates 
- "<yellow>" : Minor Update backward-compatible features 
- "<green>"  : Patch Update backward-compatible bug fixes
-Package    Current Wanted Latest Package Type    URL                                          
-docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
-✨  Done in 0.41s.
+Using globally installed version of Yarn
+yarn outdated v1.5.1
+warning package.json: No license field
+warning No license field
+info Color legend : 
+ "<red>"    : Major Update backward-incompatible updates 
+ "<yellow>" : Minor Update backward-compatible features 
+ "<green>"  : Patch Update backward-compatible bug fixes
+Package    Current Wanted Latest Package Type    URL                                          
+docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
+✨  Done in 0.41s.
 

 

 
If there is no noticeable version output from the outdated commands, then you are up-to-date.

diff --git a/docs/en/1.7.1/installation/index.html b/docs/en/1.7.1/installation/index.html
index 3c0c95685d..9325226161 100644
--- a/docs/en/1.7.1/installation/index.html
+++ b/docs/en/1.7.1/installation/index.html
@@ -144,17 +144,17 @@ yarn start (or npm run start)
 
At any time after Docusaurus is installed, you can check your current version of Docusaurus by going into the website directory and typing yarn outdated docusaurus or npm outdated docusaurus.

 
You will see something like this:

 
$ yarn outdated
-Using globally installed version of Yarn
-yarn outdated v1.5.1
-warning package.json: No license field
-warning No license field
-info Color legend : 
- "<red>"    : Major Update backward-incompatible updates 
- "<yellow>" : Minor Update backward-compatible features 
- "<green>"  : Patch Update backward-compatible bug fixes
-Package    Current Wanted Latest Package Type    URL                                          
-docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
-✨  Done in 0.41s.
+Using globally installed version of Yarn
+yarn outdated v1.5.1
+warning package.json: No license field
+warning No license field
+info Color legend : 
+ "<red>"    : Major Update backward-incompatible updates 
+ "<yellow>" : Minor Update backward-compatible features 
+ "<green>"  : Patch Update backward-compatible bug fixes
+Package    Current Wanted Latest Package Type    URL                                          
+docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
+✨  Done in 0.41s.
 

 

 
If there is no noticeable version output from the outdated commands, then you are up-to-date.

diff --git a/docs/en/installation.html b/docs/en/installation.html
index aab535f51e..6724d83e8a 100644
--- a/docs/en/installation.html
+++ b/docs/en/installation.html
@@ -144,17 +144,17 @@ yarn start (or npm run start)
 
At any time after Docusaurus is installed, you can check your current version of Docusaurus by going into the website directory and typing yarn outdated docusaurus or npm outdated docusaurus.

 
You will see something like this:

 
$ yarn outdated
-Using globally installed version of Yarn
-yarn outdated v1.5.1
-warning package.json: No license field
-warning No license field
-info Color legend : 
- "<red>"    : Major Update backward-incompatible updates 
- "<yellow>" : Minor Update backward-compatible features 
- "<green>"  : Patch Update backward-compatible bug fixes
-Package    Current Wanted Latest Package Type    URL                                          
-docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
-✨  Done in 0.41s.
+Using globally installed version of Yarn
+yarn outdated v1.5.1
+warning package.json: No license field
+warning No license field
+info Color legend : 
+ "<red>"    : Major Update backward-incompatible updates 
+ "<yellow>" : Minor Update backward-compatible features 
+ "<green>"  : Patch Update backward-compatible bug fixes
+Package    Current Wanted Latest Package Type    URL                                          
+docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
+✨  Done in 0.41s.
 

 

 
If there is no noticeable version output from the outdated commands, then you are up-to-date.

diff --git a/docs/en/installation/index.html b/docs/en/installation/index.html
index aab535f51e..6724d83e8a 100644
--- a/docs/en/installation/index.html
+++ b/docs/en/installation/index.html
@@ -144,17 +144,17 @@ yarn start (or npm run start)
 
At any time after Docusaurus is installed, you can check your current version of Docusaurus by going into the website directory and typing yarn outdated docusaurus or npm outdated docusaurus.

 
You will see something like this:

 
$ yarn outdated
-Using globally installed version of Yarn
-yarn outdated v1.5.1
-warning package.json: No license field
-warning No license field
-info Color legend : 
- "<red>"    : Major Update backward-incompatible updates 
- "<yellow>" : Minor Update backward-compatible features 
- "<green>"  : Patch Update backward-compatible bug fixes
-Package    Current Wanted Latest Package Type    URL                                          
-docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
-✨  Done in 0.41s.
+Using globally installed version of Yarn
+yarn outdated v1.5.1
+warning package.json: No license field
+warning No license field
+info Color legend : 
+ "<red>"    : Major Update backward-incompatible updates 
+ "<yellow>" : Minor Update backward-compatible features 
+ "<green>"  : Patch Update backward-compatible bug fixes
+Package    Current Wanted Latest Package Type    URL                                          
+docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
+✨  Done in 0.41s.
 

 

 
If there is no noticeable version output from the outdated commands, then you are up-to-date.

diff --git a/docs/en/next/installation.html b/docs/en/next/installation.html
index 7462ddfa11..9505ba56e7 100644
--- a/docs/en/next/installation.html
+++ b/docs/en/next/installation.html
@@ -144,17 +144,17 @@ yarn start (or npm run start)
 
At any time after Docusaurus is installed, you can check your current version of Docusaurus by going into the website directory and typing yarn outdated docusaurus or npm outdated docusaurus.

 
You will see something like this:

 
$ yarn outdated
-Using globally installed version of Yarn
-yarn outdated v1.5.1
-warning package.json: No license field
-warning No license field
-info Color legend :
- "<red>"    : Major Update backward-incompatible updates
- "<yellow>" : Minor Update backward-compatible features
- "<green>"  : Patch Update backward-compatible bug fixes
-Package    Current Wanted Latest Package Type    URL
-docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
-✨  Done in 0.41s.
+Using globally installed version of Yarn
+yarn outdated v1.5.1
+warning package.json: No license field
+warning No license field
+info Color legend :
+ "<red>"    : Major Update backward-incompatible updates
+ "<yellow>" : Minor Update backward-compatible features
+ "<green>"  : Patch Update backward-compatible bug fixes
+Package    Current Wanted Latest Package Type    URL
+docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
+✨  Done in 0.41s.
 

 

 
If there is no noticeable version output from the outdated commands, then you are up-to-date.

diff --git a/docs/en/next/installation/index.html b/docs/en/next/installation/index.html
index 7462ddfa11..9505ba56e7 100644
--- a/docs/en/next/installation/index.html
+++ b/docs/en/next/installation/index.html
@@ -144,17 +144,17 @@ yarn start (or npm run start)
 
At any time after Docusaurus is installed, you can check your current version of Docusaurus by going into the website directory and typing yarn outdated docusaurus or npm outdated docusaurus.

 
You will see something like this:

 
$ yarn outdated
-Using globally installed version of Yarn
-yarn outdated v1.5.1
-warning package.json: No license field
-warning No license field
-info Color legend :
- "<red>"    : Major Update backward-incompatible updates
- "<yellow>" : Minor Update backward-compatible features
- "<green>"  : Patch Update backward-compatible bug fixes
-Package    Current Wanted Latest Package Type    URL
-docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
-✨  Done in 0.41s.
+Using globally installed version of Yarn
+yarn outdated v1.5.1
+warning package.json: No license field
+warning No license field
+info Color legend :
+ "<red>"    : Major Update backward-incompatible updates
+ "<yellow>" : Minor Update backward-compatible features
+ "<green>"  : Patch Update backward-compatible bug fixes
+Package    Current Wanted Latest Package Type    URL
+docusaurus 1.0.9   1.2.0  1.2.0  devDependencies https://github.com/facebook/Docusaurus#readme
+✨  Done in 0.41s.
 

 

 
If there is no noticeable version output from the outdated commands, then you are up-to-date.

diff --git a/img/slash-introducing.svg b/img/slash-introducing.svg
index ade6a0cacd..b6657d74c1 100644
--- a/img/slash-introducing.svg
+++ b/img/slash-introducing.svg
@@ -1 +1 @@
-
\ No newline at end of file
+
\ No newline at end of file