From 5981ef1251a2e40cde32b16765a37a9aa2e09d06 Mon Sep 17 00:00:00 2001 From: Website Deployment Script Date: Thu, 14 Jun 2018 23:19:36 +0000 Subject: [PATCH] Deploy website Deploy website version based on fee10658065f47bfca68b835c0ca27fd548d5f28 --- docs/en/next/publishing.html | 3 ++- docs/en/next/publishing/index.html | 3 ++- docs/es-ES/next/publishing.html | 3 ++- docs/es-ES/next/publishing/index.html | 3 ++- docs/ro/next/publishing.html | 3 ++- docs/ro/next/publishing/index.html | 3 ++- docs/tr/next/publishing.html | 3 ++- docs/tr/next/publishing/index.html | 3 ++- docs/zh-CN/next/publishing.html | 3 ++- docs/zh-CN/next/publishing/index.html | 3 ++- 10 files changed, 20 insertions(+), 10 deletions(-) diff --git a/docs/en/next/publishing.html b/docs/en/next/publishing.html index bc65c39a5f..d735be5985 100644 --- a/docs/en/next/publishing.html +++ b/docs/en/next/publishing.html @@ -82,7 +82,8 @@
-

Docusaurus also supports deploying user or organization sites. These sites will be served from the master branch of the repo. So, you will want to have the Docusaurus infra, your docs, etc. in another branch (e.g., maybe call it source). To do this, just set projectName to "username.github.io" (where username is your username or organization name on GitHub) and organizationName to "username". The publish script will automatically deploy your site to the root of the master branch to be served.

+

Docusaurus also supports deploying user or organization sites. To do this, just set projectName to "username.github.io" (where username is your username or organization name on GitHub) and organizationName to "username".
+For user or org sites, the publish script will deploy these sites to the root of the master branch of the username.github.io repo. In this case, note that you will want to have the Docusaurus infra, your docs, etc. either in another branch of the username.github.io repo (e.g., maybe call it source), or in another, separated repo (e.g. in the same as the documented source code).

While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.

diff --git a/docs/en/next/publishing/index.html b/docs/en/next/publishing/index.html index bc65c39a5f..d735be5985 100644 --- a/docs/en/next/publishing/index.html +++ b/docs/en/next/publishing/index.html @@ -82,7 +82,8 @@
-

Docusaurus also supports deploying user or organization sites. These sites will be served from the master branch of the repo. So, you will want to have the Docusaurus infra, your docs, etc. in another branch (e.g., maybe call it source). To do this, just set projectName to "username.github.io" (where username is your username or organization name on GitHub) and organizationName to "username". The publish script will automatically deploy your site to the root of the master branch to be served.

+

Docusaurus also supports deploying user or organization sites. To do this, just set projectName to "username.github.io" (where username is your username or organization name on GitHub) and organizationName to "username".
+For user or org sites, the publish script will deploy these sites to the root of the master branch of the username.github.io repo. In this case, note that you will want to have the Docusaurus infra, your docs, etc. either in another branch of the username.github.io repo (e.g., maybe call it source), or in another, separated repo (e.g. in the same as the documented source code).

While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.

diff --git a/docs/es-ES/next/publishing.html b/docs/es-ES/next/publishing.html index d517f4f7cf..7629f41a40 100644 --- a/docs/es-ES/next/publishing.html +++ b/docs/es-ES/next/publishing.html @@ -80,7 +80,8 @@
-

Docusaurus also supports deploying user or organization sites. These sites will be served from the master branch of the repo. So, you will want to have the Docusaurus infra, your docs, etc. in another branch (e.g., maybe call it source). To do this, just set projectName to "username.github.io" (where username is your username or organization name on GitHub) and organizationName to "username". The publish script will automatically deploy your site to the root of the master branch to be served.

+

Docusaurus also supports deploying user or organization sites. To do this, just set projectName to "username.github.io" (where username is your username or organization name on GitHub) and organizationName to "username".
+For user or org sites, the publish script will deploy these sites to the root of the master branch of the username.github.io repo. In this case, note that you will want to have the Docusaurus infra, your docs, etc. either in another branch of the username.github.io repo (e.g., maybe call it source), or in another, separated repo (e.g. in the same as the documented source code).

While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.

One of the required parameters is set as a environment variable:

diff --git a/docs/es-ES/next/publishing/index.html b/docs/es-ES/next/publishing/index.html index d517f4f7cf..7629f41a40 100644 --- a/docs/es-ES/next/publishing/index.html +++ b/docs/es-ES/next/publishing/index.html @@ -80,7 +80,8 @@
-

Docusaurus also supports deploying user or organization sites. These sites will be served from the master branch of the repo. So, you will want to have the Docusaurus infra, your docs, etc. in another branch (e.g., maybe call it source). To do this, just set projectName to "username.github.io" (where username is your username or organization name on GitHub) and organizationName to "username". The publish script will automatically deploy your site to the root of the master branch to be served.

+

Docusaurus also supports deploying user or organization sites. To do this, just set projectName to "username.github.io" (where username is your username or organization name on GitHub) and organizationName to "username".
+For user or org sites, the publish script will deploy these sites to the root of the master branch of the username.github.io repo. In this case, note that you will want to have the Docusaurus infra, your docs, etc. either in another branch of the username.github.io repo (e.g., maybe call it source), or in another, separated repo (e.g. in the same as the documented source code).

While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.

One of the required parameters is set as a environment variable:

diff --git a/docs/ro/next/publishing.html b/docs/ro/next/publishing.html index 443e271d73..03dae35619 100644 --- a/docs/ro/next/publishing.html +++ b/docs/ro/next/publishing.html @@ -80,7 +80,8 @@
-

Docusaurus also supports deploying user or organization sites. These sites will be served from the master branch of the repo. So, you will want to have the Docusaurus infra, your docs, etc. in another branch (e.g., maybe call it source). To do this, just set projectName to "username.github.io" (where username is your username or organization name on GitHub) and organizationName to "username". The publish script will automatically deploy your site to the root of the master branch to be served.

+

Docusaurus also supports deploying user or organization sites. To do this, just set projectName to "username.github.io" (where username is your username or organization name on GitHub) and organizationName to "username".
+For user or org sites, the publish script will deploy these sites to the root of the master branch of the username.github.io repo. In this case, note that you will want to have the Docusaurus infra, your docs, etc. either in another branch of the username.github.io repo (e.g., maybe call it source), or in another, separated repo (e.g. in the same as the documented source code).

While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.

One of the required parameters is set as a environment variable:

diff --git a/docs/ro/next/publishing/index.html b/docs/ro/next/publishing/index.html index 443e271d73..03dae35619 100644 --- a/docs/ro/next/publishing/index.html +++ b/docs/ro/next/publishing/index.html @@ -80,7 +80,8 @@
-

Docusaurus also supports deploying user or organization sites. These sites will be served from the master branch of the repo. So, you will want to have the Docusaurus infra, your docs, etc. in another branch (e.g., maybe call it source). To do this, just set projectName to "username.github.io" (where username is your username or organization name on GitHub) and organizationName to "username". The publish script will automatically deploy your site to the root of the master branch to be served.

+

Docusaurus also supports deploying user or organization sites. To do this, just set projectName to "username.github.io" (where username is your username or organization name on GitHub) and organizationName to "username".
+For user or org sites, the publish script will deploy these sites to the root of the master branch of the username.github.io repo. In this case, note that you will want to have the Docusaurus infra, your docs, etc. either in another branch of the username.github.io repo (e.g., maybe call it source), or in another, separated repo (e.g. in the same as the documented source code).

While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.

One of the required parameters is set as a environment variable:

diff --git a/docs/tr/next/publishing.html b/docs/tr/next/publishing.html index f0e7f10a2a..a212012ebe 100644 --- a/docs/tr/next/publishing.html +++ b/docs/tr/next/publishing.html @@ -80,7 +80,8 @@
-

Docusaurus also supports deploying user or organization sites. These sites will be served from the master branch of the repo. So, you will want to have the Docusaurus infra, your docs, etc. in another branch (e.g., maybe call it source). To do this, just set projectName to "username.github.io" (where username is your username or organization name on GitHub) and organizationName to "username". The publish script will automatically deploy your site to the root of the master branch to be served.

+

Docusaurus also supports deploying user or organization sites. To do this, just set projectName to "username.github.io" (where username is your username or organization name on GitHub) and organizationName to "username".
+For user or org sites, the publish script will deploy these sites to the root of the master branch of the username.github.io repo. In this case, note that you will want to have the Docusaurus infra, your docs, etc. either in another branch of the username.github.io repo (e.g., maybe call it source), or in another, separated repo (e.g. in the same as the documented source code).

While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.

One of the required parameters is set as a environment variable:

diff --git a/docs/tr/next/publishing/index.html b/docs/tr/next/publishing/index.html index f0e7f10a2a..a212012ebe 100644 --- a/docs/tr/next/publishing/index.html +++ b/docs/tr/next/publishing/index.html @@ -80,7 +80,8 @@
-

Docusaurus also supports deploying user or organization sites. These sites will be served from the master branch of the repo. So, you will want to have the Docusaurus infra, your docs, etc. in another branch (e.g., maybe call it source). To do this, just set projectName to "username.github.io" (where username is your username or organization name on GitHub) and organizationName to "username". The publish script will automatically deploy your site to the root of the master branch to be served.

+

Docusaurus also supports deploying user or organization sites. To do this, just set projectName to "username.github.io" (where username is your username or organization name on GitHub) and organizationName to "username".
+For user or org sites, the publish script will deploy these sites to the root of the master branch of the username.github.io repo. In this case, note that you will want to have the Docusaurus infra, your docs, etc. either in another branch of the username.github.io repo (e.g., maybe call it source), or in another, separated repo (e.g. in the same as the documented source code).

While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.

One of the required parameters is set as a environment variable:

diff --git a/docs/zh-CN/next/publishing.html b/docs/zh-CN/next/publishing.html index cf9c558cbd..bccbf90095 100644 --- a/docs/zh-CN/next/publishing.html +++ b/docs/zh-CN/next/publishing.html @@ -80,7 +80,8 @@
-

Docusaurus also supports deploying user or organization sites. These sites will be served from the master branch of the repo. So, you will want to have the Docusaurus infra, your docs, etc. in another branch (e.g., maybe call it source). To do this, just set projectName to "username.github.io" (where username is your username or organization name on GitHub) and organizationName to "username". The publish script will automatically deploy your site to the root of the master branch to be served.

+

Docusaurus also supports deploying user or organization sites. To do this, just set projectName to "username.github.io" (where username is your username or organization name on GitHub) and organizationName to "username".
+For user or org sites, the publish script will deploy these sites to the root of the master branch of the username.github.io repo. In this case, note that you will want to have the Docusaurus infra, your docs, etc. either in another branch of the username.github.io repo (e.g., maybe call it source), or in another, separated repo (e.g. in the same as the documented source code).

While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.

One of the required parameters is set as a environment variable:

diff --git a/docs/zh-CN/next/publishing/index.html b/docs/zh-CN/next/publishing/index.html index cf9c558cbd..bccbf90095 100644 --- a/docs/zh-CN/next/publishing/index.html +++ b/docs/zh-CN/next/publishing/index.html @@ -80,7 +80,8 @@
-

Docusaurus also supports deploying user or organization sites. These sites will be served from the master branch of the repo. So, you will want to have the Docusaurus infra, your docs, etc. in another branch (e.g., maybe call it source). To do this, just set projectName to "username.github.io" (where username is your username or organization name on GitHub) and organizationName to "username". The publish script will automatically deploy your site to the root of the master branch to be served.

+

Docusaurus also supports deploying user or organization sites. To do this, just set projectName to "username.github.io" (where username is your username or organization name on GitHub) and organizationName to "username".
+For user or org sites, the publish script will deploy these sites to the root of the master branch of the username.github.io repo. In this case, note that you will want to have the Docusaurus infra, your docs, etc. either in another branch of the username.github.io repo (e.g., maybe call it source), or in another, separated repo (e.g. in the same as the documented source code).

While we recommend setting the projectName and organizationName in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.

One of the required parameters is set as a environment variable: